[Plugin] Custom Toolbars Plugin

Dave R

@xiombarg said:

Having quick access for toggling on/off hidden geometry, work lines, hide rest of model, perspective and a few other of my most often used tools is invaluable to me.
this is exactly the 50% of the reason why i stay with SU8 for now.

Why can't you do it with SU2013 or SU2014? I have keyboard shortcuts for toggling visibility of those things that were set up in SU6 and I've continued to use them for all versions since then.

Box

Plus you can customise native and plugin toolbars.

And this plugin does work in 2014

panixia

@dave r said:

Why can't you do it with SU2013 or SU2014? I have keyboard shortcuts for toggling visibility of those things that were set up in SU6 and I've continued to use them for all versions since then.

sure, i know you can do this by keyboard shortcuts.. but i like to do this sort of thing with toolbars buttons, having basically any sort ofshortcuts + modifier combo (ctr+alt+...) already assigned to tons of tools/plugins and so on..

panixia

@box said:

And this plugin does work in 2014

are you sure?
i didn't try 2014, but i remember when i tried 2013 it didn't work for me..

Box

@panixia said:

@box said:

And this plugin does work in 2014

are you sure?
i didn't try 2014, but i remember when i tried 2013 it didn't work for me..

I wouldn't answer a question if I hadn't checked the answer.

BTW it also works in 2013. and yes I have installed and checked it.

xiombarg

@dave r said:

Why can't you do it with SU2013 or SU2014? I have keyboard shortcuts for toggling visibility of those things that were set up in SU6 and I've continued to use them for all versions since then.

I like to have buttons for things that I use fairly often but not often enough that I have the shortcuts programmed into my fingertips. Thos being the case, it's faster for me to have the buttons instead of pausing to remember what the shortcut is and having to try a couple of keys before I finally get it.

Otherwise you are right. Shortcuts are always faster, as long as you remember what they are.

xkalvisx

And where is the key "Make component"?

Jim

Not all SketchUp commands are available from the Ruby API. If the API does not support a command, as it does not with Make Component, then the command will need to be recreated from the beginning. It is possible to recreate the Make Component command in Ruby. I will work on it this coming week, unless someone has already written such and and would be kind enough to share it.

Box

I'm a bit confused Jim, Make component is available in your toolset.
Perhaps the question is what Key stroke is Make Component, the default for that is g.

Jim

@box said:

I'm a bit confused Jim, Make component is available in your toolset.
Perhaps the question is what Key stroke is Make Component, the default for that is g.

Heh, so it is. it's called "makeComponent" of all things.

Unfortunately, it uses a send_action which does not appear to work in SketchUp 2014.

Box

Works perfectly in my version of 2014.

Jim

Ah, it opens the dialog when loose geometry is selected. I had selected a Group. Thanks.

Bob James

Tried both 'standard' plugin location and additional location.

Jim

Hello Bob,

You need to install TIG's Purge All plugin.
I thought I trapped that error.

Will look into it. Thanks for taking time to report.

Jim

Bob, I posted a new version this morning in the Plugin Store, but didn't have time to mention it. Did you find and try the update?

You still need to install TIG's purge_all plugin for the custum button to work.

derei

The "viewRedo" message for Sketchup.send_action, seems unimplemented in API and not present in standard Camera toolbar, but is available in Camera drop-down menu. May be just an omision from Trimble, or it was intended to not be available? Any reasons for that?
I remember a time when it was, and I had it on my Custom Toolbar.

Dan Rathbun

Yes it was removed in SU2013 or SU2014 (can't remember which.)

SketchUp used to remember a whole bunch of camera views, and the "viewUndo:" button would go backwards in the stack. The "viewRedo:" button would go forward in the stack.

Now only the current and previous views are saved. The "viewUndo:" ("View Previous") button just switches between them.

I don't remember why they said the memory stack was removed. We didn't like the change at the time. Could be that in practice not many used the feature, ie only went one view back, etc. Or they were just simplifying the codebase.

Hmmm.. thinking more,... I think the change had to do with avoiding ViewObserver crashes or complexities.

derei

I see, thanks for clearing it out. For me was a very good asset. It didn't remembered too many views. I think it was about 5. But it was helpful when experimenting with views, for rendering. Sometimes I just wanted to see if another view was better, but then, I decided to go back... Now I'll just have to stick to the current limitations.

Dan Rathbun

There might be some plugins... someone made a Camera Memory plugin I think.

jgb

I am almost converted to SU-15 from SU-8.
I just realized that many of my SU-8 toolbars (especially "toggle/hidden") are not native SU but within Toolbars.rb.

How can I import the toolbars.rb set to SU-15?

I can't find the current file here.