Quick Selection

Dave R

It throws up this error message for me. I expect Didier needs to update it.

Error: #<SyntaxError: <main>: unterminated string meets end of file> -e:1:ineval'
nil`

paddyclown

oh, ok, thanks; all gobbldy-gook to me

hope there's un update in the pipeline 'cos it a very good plugin...

Box

Tig posted a fix for some of Didier's plugins, it may work for this one too.

@unknownuser said:

Didier needs to rework his rb file for v2014 compatibility and republish it...

BUT you can do it temporarily for your own use, even though his script is 'packed'.
Open the file lines2tubes.rb in Notepad, and go to the end:
Change
...}.unpack("m").to_s
to read
...}.unpack("m")[0]
Save the changes.
Restart SketchUp.

The script will then load and work in v2014 !

This simple fix can be applied to any of Didier's 'packed' scripts that aren't working in v2014.

These edited scripts will also load and work in earlier SketchUp versions too...

paddyclown

thankyou, that worked for me !

paddyclown

Hi,

All worked for a while in 2014, but in 2015 and last updated version 2014, I get this error when trying to use the quick selection tool...

"Starting quick selection...
Parsing objects with option: All visible objects
Error: #<NameError: uninitialized constant Set>
(eval):63:in build_searchable_entities' (eval):495:in quick_selection'
(eval):691:in qs' (eval):710:in block in <top (required)>'
-e:1:in `call'"

any ideas please ?

driven

@paddyclown said:

Error: #<NameError: uninitialized constant Set>

Sketchup removed Set it now users Sketchup::Set

you could add

require('set')

at the top of the script...

it may then work, otherwise it needs a proper fix...
john

paddyclown

John, Thanks for the idea... it just made SU bugsplat on start... so i undid the change in order to work; I guess we just have to hope D Bur has a moment to update this plugin which was brilliant !

Jim

You can replace all occurrences in the script from Set.new with Sketchup::Set.new

paddyclown

Jim,
Thankyou ! BingoBongo it works !
best,

Jim

@driven said:

would it not be better to do a search and replace changing Set to Sketchup::Set in the script...

Yes.

I edited my example to remove the code snippet - it's a very bad idea.

thomthom

@driven said:

@jim said:

This should work.


> > if defined?(Sketchup;;Set)
> >   Set = Sketchup;;Set
> > end
> >

I was going to suggest that, but what happens if another ruby has already used require 'set'?

would it not be better to do a search and replace changing Set to Sketchup::Set in the script...
john

That shim should be done in the extension namespace - then it's all fine. It should NOT be done in the global namespace as that will clash.

Jim

I edited my snippet - it was a bad example without the namespace.

Better to just find and replace Set.new with Sketchup::Set.new

driven

@jim said:

This should work.


> Edit; removed Jim's example
>

I was going to suggest that, but what happens if another ruby has already used require 'set'?

would it not be better to do a search and replace changing Set to Sketchup::Set in the script...
john