@mitcorb said: Dale, would that be a Fender Coronado in that picture? Never played one, but drooled over them back in the day. You nailed it. Discontinued in the early 70's. Typical Fender headstock. All other semi hollow bodies of the day had that blocky Gibson like headstock. After John Lennon used his Epiphone Casino to record the White Album and Let it Be, semi hollows were all the rage, and it is said this was Fenders entry into that market. [image: 78Yl_Screenshot2012-02-04at6.15.52AM.png]

Curieux, j'avais téléchargé exactement la même version (en anglais), désinstallé SU puis réinstallé, et il m'avait demandé d'installer la nouvelle version (8.1 je présume), qui s'est avéré être en français. Et là je recommence, et ça fonctionne... Bon. Bref. Tant mieux si cela fonctionne ! Merci à toi Laurent !

Awesome textures guys! Thanks!

Hi Dan and Chris. Thank you for your answers ! @chris said: Well, those braces can be expanded to as many lines of code as you would like. You could write it like this: Yes, but I wanted to have a automated method... no need to write Module::Sub_module.method, just copy a line that returns current method in the ruby console. @dan said: Why not just open the rb in an editor, and find the command in the file ? that's what I do when I search the command. But I am not sure a "non-ruby" user could find this command easily. @unknownuser said: BTW.. sometimes there is good reason for a command to be kept private, a commercial plugin, or a Pro only plugin. The writer of a plugin, has the right, to not allow their plugin (or it's tools,) to be called in ways that could defeat the license, or cause other problems. I am not saying this bit of code MUST be inserting in each plugin, of course... Just for MY personal plugins, because I like transparency.. I just asked this forum if someone had a better (or a native) way to do like my little method...

Here is a preview of the new version of cartouche plugin: [image: V1Q5_Cartouche.jpg] I don't have time to test it, and have a problem with preview window. But I would put it for download soon.

I didn't realise there was a $ script already ! Sorry RickW... but my version is out there now... $5 x X for a few seconds work ?

Matthieu, thank you so much.

@dave r said: Why don't you write a better version, then? I agree... BUT this one is SIX years old ! And time and expertise moves on... There are by now many similar tools around... e.g. 2dTools 'Adjust'... OR you could write a better 'free' one...

Ah! That's a good idea!

I'm guessing you already have a tool observer set up or something? You've already figured out how to keep track of the previously used tools, right? If so, Lets say you have a global variable that holds an array of all the last used tools - $previous_tools Also, maybe you need a menu item for "Set Shortcut Key". This is for the user to tell your script what key they have assigned your script to (it might save the value to an external text file or a registry entry would be better). So perhaps they assign it to "t", your inputbox could create a global variable $previous_tools_shortcut = "t" Now make a tool with the onKeyUp method in it. It compares the onkey up to $previous_tools_shortcut. And it also implements its own timer feature. So you can watch the time between keystrokes. So if they press the dhortcut key 1 time, it just selects $previous_tools.last. If they press it twice within a specified time limit (.5 seonds or less) then it will select $previous_tools[length-1], press it three times within 1 second, it selects the $previous_tools[length-2] tool. That is how I think I would go about it. But that assumes you have an array of the previously used tools, and it also requires the user to input the shortcut key that they assigned to your tool. Chris

I thought about that work-around method... I will use it until something better... Thank you Chris!

Excellent, glad it helped (and worked). I also just edited a minor typo in the example, but I'm sure you figured it out even with the typo, Chris

Starting from Jim's SketchUp-Ruby Resources, what about tag plugins by classes ? For example: Mechanical tools, Architecture tools, Kinematics tools, Geometry creation tools, Geometry Modification tools, Measurement tools, (running out of imagination), but I'm sure there could be a nice group of classes out there. Having plugins organized by classes, maybe we can extract more conclusions about wants and needs. Regards Marcio

I suppose if the user is using this plugin they already have a good idea of what its going to look like, so showing them isnt neccesary. More generally, most people just use common sense.

am i doing something wrong, or is it not possible to open the "selection manager" dialog box on a mac osx machine?

Thanks sdmitch, used your code snippet to convert components to groups for MSPhysics. The reason is that MSP does not accept components for coupling with joints. The conversion of about 200 components with subcomponents into groups would have taken a long time...

Aaah... Cool!

Ah, Ok! Thank you for theses explanations!

You could overwrite the add_toolbar and toolbar_names methods of Sketchup. But you have to make sure that your plugin is the first loaded. azuby