[Plugin] LaunchUp – A Quick Launcher for SketchUp

Aerilius · 30 Apr 2013, 10:46

Please update LaunchUp as soon as possible!
It contains fixes for menu gray-out avoidance.
Thank you.

Rich O Brien · 30 Apr 2013, 10:51

Added update to store

function · 30 Apr 2013, 17:07

oh man i was wondering why that was happening! Thanks for the update

glro · 1 May 2013, 12:41

@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...

Pete · 1 May 2013, 22:17

@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.

Aerilius · 2 May 2013, 11:00

I found it and fixed it in 1.0.11.

glro · 2 May 2013, 12:45

@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?

EscapeArtist · 2 May 2013, 13:16

^^^ 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?

Aerilius · 2 May 2013, 14:07

"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)?

glro · 2 May 2013, 14:27

@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

EscapeArtist · 3 May 2013, 02:52

Fascinating. It works fine now. Please disregard the previous. Restarted SU.

Anton_S · 9 May 2013, 02:49

Hey, AE

LaunchUp is truly beneficial to use , but how should I get around the submenu.set_validation_proc(item)? It seems not to work anymore on my pc

I have ae_LaunchUp_1_0_11.rbz

Edit:Installed ae_LaunchUp_1_0_13.rbz, everything seems to work great now. Once again, thank you for the awesome plugin

lionk · 10 May 2013, 00:14

thank you! AE!
DBCS bug is fixed now.

lionk · 12 May 2013, 10:15

"Search…" is missing when open LaunchUp since ver 1.0.11.
in IE9...

Aerilius · 15 May 2013, 02:09

I found why the placeholder text disappeared and added it back. And I updated the webdialog for higher dpi settings.

ephi · 23 May 2013, 12:17

cool tool

bsintzel · 21 Jun 2013, 17:47

Thanks for the tip. I'll give it a go. I suspect what I'm asking for would really require a GUI redesign.

masterpaul · 10 Dec 2013, 05:05

For some reason launchup fails to find any plugin.

Edit: Problem fixed after I gave sketchup full administrative powers.

vicxp0518 · 19 Feb 2014, 08:12

I've figured out that this plugin will cause a major slow down with selecting, component editing, layer visibility switching, and something else.

I hope I was wrong but when I suffer with the annoying problem, there seems no way out, but when I disable this plugin, everything gets back to fine normal. I don't know why this would happen, but it really occurs on my larger models.

Aerilius · 19 Feb 2014, 17:29

I will look into it. Though I don't know what could cause this (the plugin does not use observers, and should not be triggered when you change a layer etc.). Can you tell me how many plugins you have and how components and layers in the model?