[Plugin][$] JointPushPull Interactive - v4.8a - 30 Mar 24

[brodie]

Here's what I'm getting...

https://www.dropbox.com/s/pgqmxcyoi96l8oa/2014-03-14_1045.swf

[mitcorb]

Hi, Brodie:
I can't deal with the swf, sorry. Maybe someone else?

[xiombarg]

I seem to be having problems with the option of toggling axes from world to local. It doesn't recognize local, only world. I've tried it on both working models and new file. Any clues on this?

[fredo6]

NEW RELEASE: JointPush Pull Interactive v3.2b - 17 Mar 14

JointPushPull Interactive 3.2b fixes a number of bugs related to the modes of forced planar direction, which basically did not work.
Thanks to xiombarg for signaling this problem.

See main post of this thread for Download of JointPushPull.

Fredo

[xiombarg]

I've updated everything, but it still doesn't respond to the local toggle. I've tried to go through and get rid of any unused plugin files and I've used your 'purge obsolete files' utility but to no effect.

I guess I could just re-install everything and see what happens.

[fredo6]

@xiombarg said:

I've updated everything, but it still doesn't respond to the local toggle. I've tried to go through and get rid of any unused plugin files and I've used your 'purge obsolete files' utility but to no effect.

I guess I could just re-install everything and see what happens.

Could you post or PM the model where you have the problem.

The local toggle enable to use the axes of the component which contains the picked face selected, instead of the model axes.

Fredo

[xiombarg]

Maybe I'm just doing something incorrectly? But I've never had problems with it until I last updated. It had been quite awhile since I had updated, would that make a difference?

[Dave R]

I think it's a setting thing.

[xiombarg]

Nope. Whether I have that "local button" toggled on or off it still sets itself to world. I've tried all sorts of variations of setting the axis and it always resorts to world axis. It almost seems like another script is overriding it as a precedence.

[Dave R]

Two options come to mind, then. Make a new, temporary Plugins folder. Rename the orignal Old Plugins or something. Then install fresh copies of JPP and LibFredo6 to that folder. See what you get.

Or, remove all the other plugins from the current one until you find something that conflicts.

[xiombarg]

Right, that's probably what it's come to. I was just hoping that maybe I was overlooking something.

[Dave R]

What if you "press" the button below the X in red? That's different in my screen shot compared to yours.

[dtrarch]

Dear Fredo

If it is at all possible please make the old JPP version work in SU2014?
The old version was so elegant and simple and while the new and improved will do more, for me it just crashes, loses object elements and the settings do not do what they are told to do.
I will be pleased to the first to add to your cookie jar if we could have the option to choose the JPP version to install.
SU user since V2 and honestly I did install the new JPP properly too.
I cleaned out the old version (.....roaming/sketchup and such as well)

Thanks and please

dtr

[xiombarg]

@dave r said:

What if you "press" the button below the X in red? That's different in my screen shot compared to yours.

Pushing the button below the "X" makes it so that is doesn't lock to any specific axis? That works fine when I use it. It's the locking to a local axis that doesn't work.

Here's the current update:
So I tried uninstalling SU8 and reinstalling it and only loading Libfredo6 and Joint Push Pull and no other plugins installed... It still doesn't work. I'm at a total loss now. I thought for sure that would fix it, but nope.

I can try anything if anyone has any ideas?

[fredo6]

@dtrarch said:

Dear Fredo

If it is at all possible please make the old JPP version work in SU2014?
The old version was so elegant and simple and while the new and improved will do more, for me it just crashes, loses object elements and the settings do not do what they are told to do.
I will be pleased to the first to add to your cookie jar if we could have the option to choose the JPP version to install.
SU user since V2 and honestly I did install the new JPP properly too.
I cleaned out the old version (.....roaming/sketchup and such as well)

Thanks and please

dtr

The old version (v2.1a) is still available at the following post.

It is compatible with SU2014.

You can run the new and old versions concurrently.

Fredo

PS: do you get bugsplats or intercepted crashes (with a clean dialog box)? And If so, is it during the geometry generation?

[dtrarch]

Hi Fredo

First thanks for the updated simple JPP version.
Works perfect on SU 2014
I was using the Vector tool(new)with user direction and distance selected.
Preset distance and direction were just not invoked ?
Your error panel showed when trying to extrude and in some cases the surface (topo) disappeared and ctl-z could not recover it.

I just could not get the settings to stick.
Must just be pilot error
Again thank you for all your good works

Dave

[JQL]

Hi Fredo,

I cannot thank you enough for this amazing plugin. Among every feature, the improvements you've done to follow pushpull are incredible.

There's just something that I don't know if it could be avoided or not but when I use your plugin it always leaves behind the temp layer it requires to work.

Is it possible to make the plugin auto-delete the layer after finishing command?

I know it's just a small detail and it is ridiculous of me to point it out but...

Thanks for everything,

JQL

[Dave R]

That's odd. I never noticed the temp layer before. I just gave it a try and I see that layer in the layers list but it goes way when the JPP operation has been completed.

[fredo6]

Normally, the temporary layer goes away when you exit JPP.

But if you crash JPP, then it may remain.

And, as you may know, there is no way to remove a layer (or a material) from the Ruby API (the way it is handled in JPP is via aborting the operation before generating the geometry).

So it has to be done manually, which is a safe operation.

Fredo

[TIG]

The [clunky] way to delete a layer through the API is...
First iterate model.entities and all of the definition.entities, and if they are are assigned the layer we want to delete - say ' tlayer' - then you erase! them.
Then you iterate through model.layers.to_a - [tlayer], and make a temp_group, and inside that a nested group with a cpoint in it, assign the layer to the nested group, repeat adding a copy of the group and and assigning the next layer to it etc.
Eventually all layers are 'used', except for the ' tlayer' [even previously unused layers].
Use model.layers.purge_unused to now purge ' tlayer'.
Finally use temp_group.erase! to tidy up.
It will work but as I said it's clunky...