[Plugin] LaunchUp – A Quick Launcher for SketchUp
-
I also occasionally see the "Type to search..." string under text that has been entered. Can't quite reliably reproduce it though.
-
I forgot to add:
• it is now possible to close the dialog when pressing the escape key.Isn't F5 the reload shortcut? I might have to test that reloading the JavaScript doesn't break it, or I add an override to prevent F5.
-
Ah! Duh! Yea - I wasn't thinking of that. It's just that I've used all the "normal" keys.
-
hi AE,
for some reason the dialog window always starts bottom left corner, pinned, unpinned, same session or even after I close SU with it open.
john
mac...
-
something wrong in options at "custom color"
-
well done!thanks you!
another bug...
if I type some Chinese characters like "面"(it means "face"), there will be an error in ruby console and get no search results, then unable to search again.
![Error: #<SyntaxError: (eval):1:ininitialize': compile error (eval):1: unterminated string meets end of file (eval):1: syntax error, unexpected $end, expecting ']' ["look_up", "é?￠"]#16 ^>](/uploads/imported_attachments/x92F_20130416111835.jpg "Error: #<SyntaxError: (eval):1:ininitialize': compile error
(eval):1: unterminated string meets end of file
(eval):1: syntax error, unexpected $end, expecting ']'
["look_up", "é?￠"]#16
^>")
in light of this, i found these punctuations "?()[]{}+*" also make mistakes. -
Thanks for finding that!
I also solved the custom color issue and will probably have an update later today. -
Version 1.0.8 is available:
• I fixed the issue with invalid/incomplete custom colors.
• I fixed the error with 面?()[]{}+*
• and reloading the webdialog (F5) doesn't break it anymore. -
@aerilius said:
Version 1.0.8 is available:
• I fixed the issue with invalid/incomplete custom colors.
• I fixed the error with 面?()[]{}+*
• and reloading the webdialog (F5) doesn't break it anymore.punctuation is OK but some Chinese characters still arise same error.
for example 面 领 到 认 封...not all the Chinese characters,just a few.i have no idea what caused this...encoding?
-
Version 1.0.9 contains a quick fix, please update.
-
Please update LaunchUp as soon as possible!
It contains fixes for menu gray-out avoidance.
Thank you. -
Added update to store
-
oh man i was wondering why that was happening! Thanks for the update
-
@aerilius said:
Please update LaunchUp as soon as possible!
It contains fixes for menu gray-out avoidance.
Thank you.version 10 only show native sketchup plugins on my computer; components (with CLibraries_Loader.rb) or added plugins are not proposed anymore in the launchup window
maybe i missed sometinhing...
-
@glro said:
version 10 only show native sketchup plugins on my computer; components (with CLibraries_Loader.rb) or added plugins are not proposed anymore in the launchup window
Me too. I will revert to the old version until CLibraries_Loader.rb is supported again.
-
I found it and fixed it in 1.0.11.
-
@aerilius said:
I found it and fixed it in 1.0.11.
yes; it shows components now
Some plugins still don't appear in the list, though
It seems that the plugin name is not taken into account in the search; does the plugin need something special to be recognized?
-
^^^ Yep. Is this an issue with the plugin or is the list of downloadable plugins incomplete and being updated? I was looking for "repair broken lines" and noticed it wasn't listed. If incomplete or missing, would you like any missing files listed here?
-
"Plugins" don't exist as an entity, they are just text files and Ruby evaluates all as if it was one long seamless script.
LaunchUp should recognize menu items and commands (like toolbar items) that are created after the file
%(#000000)[!LaunchUp.rb]has been loaded (it is important that it is one of the first scripts that is loaded).
So it searches menu text (+menu path), tooltip, toolbar name, and the file name of the ruby script in which the command was created. It would be easy to return all matching results, but there would be many. The challenge is to sort the results by relevance (which match best to the search term) and with error tolerance. It is possible that a result is too low in the ranking and comes up only after typing more characters.When I search "repair" I get "Repair broken lines". Can you give me the exact search terms that you enter, the commands that are missing and the plugins' names (where I can find and install them)?
-
@aerilius said:
"Plugins" don't exist as an entity, they are just text files and Ruby evaluates all as if it was one long seamless script.
LaunchUp should recognize menu items and commands (like toolbar items) that are created after the file
%(#000000)[!LaunchUp.rb]has been loaded (it is important that it is one of the first scripts that is loaded).
So it searches menu text (+menu path), tooltip, toolbar name, and the file name of the ruby script in which the command was created. It would be easy to return all matching results, but there would be many. The challenge is to sort the results by relevance (which match best to the search term) and with error tolerance. It is possible that a result is too low in the ranking and comes up only after typing more characters.When I search "repair" I get "Repair broken lines". Can you give me the exact search terms that you enter, the commands that are missing and the plugins' names (where I can find and install them)?
OK
it is just that i had not typed enough letters for the plugin to be able to be recognized by launchup
it seems to be working fine
Advertisement