[Plugin] Recurve

jeff hammond

@diggsey said:

Just updated the first post with update 1.3. It includes the changes suggested by Jeff.

wow! that's great.
it's been added to my shortcuts and has replaced my most used ruby.. so long good friend (weld)

[btw - the 'select curve and recurve' (⇧W) seems like magic ]

thanks so much!

Ben Ritter

Thank you Diggsey.

pilou

@unknownuser said:

does this perform the same function as weld?

yes and much more

Sorry but I miss something
Where is the function "weld" or similar in this plug?
How weld this with it?

Rich O Brien

Recurve Edge = Weld

Select edges - Right click - Recurve edge

pilou

Sorry that works not
I select the 2 lines + the arc then apply Right click "Recurve Edges"
That only explode my arc in segments!
Nothing is welded!
This plug don't work with the V6 ?

Edit: That works for the V7

Rich O Brien

And v8

Is it time to upgrade?

pilou

I have all versions but all my plugs (I am a Plug test pilot collector ) are on the V6!

simon le bon

Dear Pilou and Rich,

You have certainly missed this discrete announcing from Freddo for his:
Alternate directory for Plugins

@unknownuser said:

Hi,

Till SU8, Sketchup relies on a 'hard-coded' location for the Plugins, which is typically in C:\Program Files\Google\Google SketchUp X\Plugins. This has tow main drawbacks:

This Plugin folder being in the System area, it may be protected for write access. I have heard that schools and some companies usually have PCs where access to C:\ is disabled.

The Plugin directory is attached to each version of Sketchup. So if you use several SU version, in particular for transition, you have to install and then update plugins in each application domain.

Highlighted by me (simon)I have been using for a while now a small script to overcome this situation. My requirement was primarily to be able to have a single plugin directory where I could easily test SU6, SU7 and SU8 without updating files for each application..........

(read next on his thread)......

I think a lot of SketchUp users like us still use .. v6 v7 v8 (why do we keep them? that is an interesting question ) . Maintain the plugins up to date in each SU plugin directory version is effectively confusing and tiring. So Freddo's Alternate Directory seems a good solution

simon.

pilou

Not sure in this case that is this who makes fail the tool in the V6
Waiting adivice of the author

Diggsey

I'm afraid I can't find out why it doesn't work in v6 because I only have versions 7 and 8 and google only host older downloads for sketchup pro.

It could be that the method it uses simply doesn't work in v6. You can test this by making a curve and copying it. Explode the copy and then make it into a group and position it exactly over the original curve. Then explode the group. If you are left with a curve, the method should work.

thomthom

@diggsey said:

I'm afraid I can't find out why it doesn't work in v6 because I only have versions 7 and 8 and google only host older downloads for sketchup pro.

Pro reverts into Free when the trial period of over.

thomthom

I ran Recurve on SU6 - selected a set of connected edges.

Got the following error in the Ruby Console:
Error: #<NoMethodError: undefined methodbreak_edges=' for Sketchup:Module>
C:/Program Files (x86)/Google/Google SketchUp 6/Plugins/recurve.rb:213:in recurve' C:/Program Files (x86)/Google/Google SketchUp 6/Plugins/recurve.rb:247:in recurve_selection'
C:/Program Files (x86)/Google/Google SketchUp 6/Plugins/recurve.rb:361
C:/Program Files (x86)/Google/Google SketchUp 6/Plugins/recurve.rb:361:in call'

Sketchup.break_edges was added in SU7 - that's when SU started to automatically split edges. So you should be able to make a wrapper that only use these methods and still have the plugin functioning properly. Just test for Sketchup.respond_to?( :break_edges= ).

pilou

Free version of SU6 is here

TIG

I'm not even sure that using Sketchcup.break_edges=boolean has any affect inside a script...
It determines whether or not crossing edges formed manually will split automatically at their intersection... BUT crossing edges never split when made in code anyway ??

thomthom

@tig said:

I'm not even sure that using Sketchcup.break_edges=boolean has any affect inside a script...
It determines whether or not crossing edges formed manually will split automatically at their intersection... BUT crossing edges never split when made in code anyway ??

I've wondered that myself! I find it confusing when making edges via the API, some times they seems to split - some times not.

Diggsey

I've updated the first post with a new version which will work with SketchUp 6.

pilou

Many thanks! You rocks

jeff hammond

hey diggsey

i'm curious about what angle you have the cut-off(?) set to when using 'select curve' (for instance, you can't use select curve on one side of a square and have the whole thing select)

i like that it acts the way it does but would like to know the # just so i have an idea of it.
i also use TT's select tool which will select everything regardless of angle until it hits a 3-way junction which comes in handy as well depending on the situation..

like i said though -- i'm just curious
not asking you to change anything etc.
thanks

Diggsey

It uses an angle of 1 radian (~57 degrees) as the cut-off.

jeff hammond

ok, back again

so i found some discrepancies with the plugin.. i'm not sure if this behavior is desired by you (or anyone else?) but to me, i feel like recurve should work in all 5 of these instances:

i hope this file is understandable -- i'm pretty sure it's at least 5x more understandable than if i were to try to type an explanation

so would you agree that all cases shown there should recurve? (or, if it's desired behavior, can you fill me in on the type of situation where it would be wanted?)

thanks for looking at it..