[Plugin] LaunchUp – A Quick Launcher for SketchUp
-
Excuse me, I didn't read all the post.
I'll wait the new version compatible with SU2014. -
I finished the update!
-
@vicxp0518 said:
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.
i am experiencing slowdown of sketchup also, with the last version
Have to desinstal it because i cannot use anymore my other plugins...
-
@aerilius said:
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?
Maybe launchup is not responsible for the slowdown
i have increased a lot the size of my components folder, recently; one folder is 129 MB and another 102
And i use launchup together with "CLibrairies_loader.rb", to call components as well as plugins
I understand now that "CLibrairies_loader.rb" must be the one slowing down sketchup, because it has so many components to load.
-
Thank you!
I didn't find any further hint what could cause slowdowns, but if CLibraries creates menu items for components (for all components?) it could be related.
LaunchUp uses an index of all menu items. I would expect a larger index could eventually slow down the startup and the search inside LaunchUp but shouln't affect SketchUp when LaunchUp is not used.
More components could also slowdown the components browser. But as long as components are not added into the model, they shouldn't affect SketchUp's general performance when the components browser is not used.
Could you check how many plugin-created menu items there are?
c=0; ObjectSpace.each_object(UI::Command){ c+=1 }; c
-
@aerilius said:
Thank you!
I didn't find any further hint what could cause slowdowns, but if CLibraries creates menu items for components (for all components?) it could be related.
LaunchUp uses an index of all menu items. I would expect a larger index could eventually slow down the startup and the search inside LaunchUp but shouln't affect SketchUp when LaunchUp is not used.
More components could also slowdown the components browser. But as long as components are not added into the model, they shouldn't affect SketchUp's general performance when the components browser is not used.
Could you check how many plugin-created menu items there are?
c=0; ObjectSpace.each_object(UI::Command){ c+=1 }; c
i typed
c=0; ObjectSpace.each_object(UI::Command){ c+=1 }; c
i got
70 -
@Aerilius is it possible to update your awesome plugin to sketchup 2017?
thank you
-
-
I'm wondering if this plugin is being maintained, as it seems to have some connections with Toolbar Editor plugin (perhaps a reason for both acting weird in the latest SU versions?).
-
I am using sketchup 2021. After running the plugin, all other plugins give an error.
Error in C:/Users/samib/AppData/Roaming/SketchUp/SketchUp 2021/SketchUp/Plugins/!ae_LaunchUp/interception.rb:126 for add_item
break from proc-closure
C:/Users/samib/AppData/Roaming/SketchUp/SketchUp 2021/SketchUp/Plugins/!ae_LaunchUp/index.rb:138:inblock in load_menus' (eval):5:in
block in observe_instance_method'
C:/Program Files/Chaos Group/V-Ray/V-Ray for SketchUp/extension/ruby/gui/context_menu:10:inblock in init' Error in C:/Users/samib/AppData/Roaming/SketchUp/SketchUp 2021/SketchUp/Plugins/!ae_LaunchUp/interception.rb:126 for add_item break from proc-closure C:/Users/samib/AppData/Roaming/SketchUp/SketchUp 2021/SketchUp/Plugins/!ae_LaunchUp/index.rb:138:in
block in load_menus'
Advertisement