Weld.rb Not Working
-
Thanks Adam.
It's always worked for me before. I have started disabling plugins I've recently installed but so far nothing has changed. I'm thinking there's another plugin that has changed the method or something. (if that's possible.) Strange that it works on a closed loop but not on a non-closed set of lines.
Weld's been nice because I have a one key shortcut to it. Perhaps I'll have to change my shortcut.
-
@ DaveR:
A shot in the dark. Did you test Recurve, which came out recently? Isn't this, or another recent one sort of a "TurboWeld"? And my point is that maybe some code in one of these has disturbed the code in Weld? -
Good thought, Tim. I disabled recurve.rb and tried again. No workee. Actually running Weld even exploded arcs that weren't exploded before. Thanks for the suggestion, though.
-
Recurve caused that problem for a couple of other members mentioned in recent threads. Maybe you could download a fresh Weld.rb script and see if that helps?
-
the latest version of Tgi3d 'seemed' to have caused a problem with other bezier plugins the other day
when I disabled it's loader ruby the problems went away, and haven't come back when reloaded...
it seem to have been the order in which I used the tools that caused the problems...
might be worth a try, if you have it...
john
-
Recurve messed with some tools with me. Not weld though?
-
I tried disabling recurve but that didn't change anything. I tried disabling TGI3D, too but that didn't change anything. I tried a fresh install of Weld from Smustard but with no success. TIG performed some unknown magic though and all is right with Weld.
-
and now. . .all is right with the weld. . .er . .. world.
-
Weld done
-
all's weld that ends weld. . .
Heck. .. we could go all day with this!
-
Could a ruby be written that would run through all installed rubies looking for possible sources of conflict?
-
No.
The clashes are almost all so unexpected and subtle it'd be difficult.
Where a script rewrites a base class method it's easy BUT if someone rewrites say progressbar 'that's left dangling' within there own poorly structured code until it breaks a tool using the 'real' progressbar it's hard to prevent...
There are a few - like SketchyPhysics that has an occasional clash with say Mirror.rb because it seems to be doing something to mess with the 'Sketchup::Group' class - I still haven' tracked down to a satisfactory conclusion
There is an informal list of 'bad' scripts than should be avoided and others with recoded parts to avoid problems, but I really can't see how we can automate it - reading through a script to find what it's doing is sometimes difficult as it is, let alone passing the task over to 'code'....
Advertisement