There are now both options. Both the context menu and the double click. Because in Compact Skin only the context menu can be used.
I was able to reproduce the issue with your model on my end as well. Beta version 31 fixes this - it’s working correctly for me now. Please test it.
I’ve also made a few adjustments to the plugin to minimize SketchUp crashes. If SketchUp continues to crash for you, please let me know.
Beta 31 loads and runs perfectly on M1 Mac SU26. I thought the sort feature on the VM Info panel was removed, but I found the sort value is inherited from the main Tool for marker and category, nice touch. And its live update: as I drag the custom sorted marker in the main tool window, the VM Info marker gets resorted to match. I like this.
No, no… Nothing was removed from sort feature… 
. I created this new system specifically for you based on your comments and requests. So I’m glad you like it. 
I see that I can select an object in viewport and de select it’s checkmark to take it off a marker. However, would there be a way to add a shift/ alt selection in the Match Marker tool to be able to quick remove markers from objects so that in the course of organization one doesn’t have to return to the main dialogue?
Also, model just started crashing on newest Beta:
#1776470
#1776474
#1776480
I had used BoolTools extension the first time and thought perhaps there was a conflict, however the last one I did not use the extension and it still crashed. The only new thing is the Beta
I’ll send you a private message.
Bonjour, je souhaite devenir bêta testeur. Est-il possible d’attribuer un niveau à un objet ou une catégorie, et de configurer un raccourci clavier pour changer de niveau, passer d’un niveau à un autre, sans ouvrir de boîte de dialogue ? Votre projet semble très intéressant pour sortir de la limitation de sketchup. J’ai hâte de le tester.
Bonjour, je souhaite participer au programme de bêta-test. Pourriez-vous me préciser s’il est possible d’attribuer un niveau à un objet ou une catégorie, ainsi que de configurer un raccourci clavier permettant de modifier ce niveau sans avoir à passer par une boîte de dialogue ? Votre projet paraît particulièrement prometteur pour dépasser les limites de SketchUp, et j’attends avec intérêt la possibilité de l’essayer.
I’ll send you a private message.
A member of the discussion forum has already asked me specifically about this option to assign keyboard shortcuts so that the dialog box doesn’t have to be opened. I don’t have anything like that there yet; for now, we all use the dialog box for assigning shortcuts.
I can imagine that this could be added to the plugin, but I haven’t actually used anything like that yet—not even with native tags—and I don’t know if it’s even possible to program. I mostly use standard keyboard shortcuts for modeling and commands. I use them quite a lot, but so far it hasn’t occurred to me to use keyboard shortcuts specifically for assigning markers or tags.
If you describe more precisely how it should work and what you expect from it, I’ll set it aside and try to incorporate it in future versions. But for now, I can’t promise whether it’s feasible or whether SketchUp’s API environment can support it. I know that some users on Windows use AutoHotkey for this. Maybe it could work for now, until it’s programmed into the plugin this way as well. In any case, please try to describe it to me in more detail so I don’t come up with a solution that isn’t exactly what you have in mind.
.
New Beta 32 is out - Focus on Stability and Reliability
.
I won’t be at my computer much next week because I’m on vacation. If you have any bug reports or suggestions for improvements, please send them to me, but I’ll probably respond later.
.
https://share.note.sx/6azjbi17#MjUqnDV3+JgAyXPLqTiwN2eIohrr4nwdER64xgPu6Mg
Assigning keyboard shortcuts is not exposed to the Ruby API as doing so is considered a user activity. If extension’s did this they could likely override a user’s desired shortcuts or the native SketchUp shortcuts.
All an extension can do is create menu commands that users can use to manually assign shortcuts.
I agree with Dan. Assigning shortcuts should be done on a manual basis by the user. And each separate command can be assigned by user as needed. It would be helpful after assignment to have the defined shortcut key to be displayed in the interface (like in SU menu). These commands are already available to the user:
That’s exactly why I’m creating those menu items - so I can assign keyboard shortcuts to them. But as for the requirement to assign very specific Markers or Tags - I can’t quite imagine how that would work yet, because essentially it would have to be generated automatically in the menu somehow so that the shortcuts could be assigned. That’s why I wrote that I don’t know if something like that is even possible.
And @DanRathbun essentially confirmed my assumption.
In theory, it might be possible to create a special plugin tool that would generate these menu items after restarting SketchUp?
@Laurent_2026 Or maybe somtething like this extension?
Something like this could be implemented for both markers and tags, perhaps as a unified system.
For example, an option like “Add to Quick Shortcuts” or something similar could be added to a marker’s context menu. Then there would be a dedicated shortcut that would display only the necessary items in the context menu.
Alternatively, there could be a fixed number of slots. For example, let’s say we could define 20 shortcuts this way - some for tags and some for markers. I simply don’t expect anyone to want more than 20 specialized shortcuts for assignment. It would be more for frequently used items. These slots would therefore be permanently in the menu, and the user would assign, for example, only that specific marker to that specific slot.
I can imagine it this way, or maybe not - these are just thoughts for now.
Yes, I think the gap is that in the tool we are clicking on a marker that we created and named manually, that would be difficult to target inside the plugin after deployment. It would possibly need to assign a variable when a marker is created and store that in permanent memory that can be targeted after a restart possibly. But that seems a large task. And the tool already makes it so easy to click to control from the interface. Another option would combine a check in the tool with a shortcut, but again… your tool makes most tasks a single click - wondering what will be gained by adding a shortcut key.
Oh, I see. The pop up (triggered by shortcut key) shows a dynamic list of markers already created you can choose from, and an “add new” option as well. That might work
This would free up more screen space, since the interface wouldn’t be open. At the same time, when the interface isn’t open, calculations and synchronization with the interface don’t take place, which can cause some slowdown when working with large objects and models.
So it might make sense. For example, if someone frequently selects 2–3 tags - such as “ground floor,” “upper floor,”. OR “new state,” or “old state” - they wouldn’t need to keep the interface turned on all the time for that purpose. In that case, it would make sense.
Speaking of context menus, an extension can add a context menu handler that can build menu items on-the-fly for quick assignment of properties to the item selected. This popup context menu can serve in place of shortcuts, OR the user can assign keyboard shortcuts to context commands when the context menu is displayed.
Yes, it could. Say for example you save a small list of tags or markers into a JSON file. Whilst your extension starts up it can open the file, parse it to a Ruby Hash, then iterate the hash adding the menu commands to your extension’s submenu (or submenu of the submenu, etc.)
The main issue we’ve been having is that there is no “lookup” method to get a reference to a submenu object that is already created. So your code must add new items to your menu during the startup phase when the reference to the menu is valid. When the extension registrar script returns from loading your extension, the menu reference is no longer valid.