Liserok Visibility Manager [Multi-Tagging] - Beta Testing

Just a quick check in, preliminary use is stable on Sketchup Pro 2021. I don’t really use the hide/ unhide commands w/ shortcut keys. I was curious about your usage of those shortcuts as I always understood them to be used in the course of work for quick hide/ unhide operations (ie: get rid of something temporarily and then bring it back) versus setting up scenes and states of objects based on phase of project etc (ie, using the checkmark/ eyeball icon to set up particular informative phases: demolition, new construction etc).

The above doesn’t have anything to do with the stability of the extension, however, I was curious as to your particular workflow in conjunction with your extension.

More soon hopefully helpful on the testing front!

WB

Strange change while opening this beta19. My markers changed names somehow. All the R01 changed to C01 and the C01 changed R01 (the first letters swapped). I have a few files for testing and other files seem ok. Just strange, was easy to change back as I only had 15 items.

Functional question: Is there a way to indicate when a marker is selected (clicking the mouse icon), can the green indicator on the right be a different color maybe? If we only select a single marker it shows the Checkbox checked, and if multiple markers are checked the checkbox shows a dash for multiple, but if you want to deselect the one you selected is not easily identified.

@mark.perrah The name change in version 19 doesn’t make sense. I only changed the .css Skins, where I only tweaked the interface colors.

Didn’t version 18 do this?

Nothing like that happened to my models.

Clicking on the mouse icon (Select) selects all objects with this Marker in the model.
And clicking on the icon again deselects all objects with this Marker. It is a cyclic command

If you select objects that have the same Markers assigned, a check mark indicator appears next to the given Marker.

If the objects you select do not all have the given marker - there is a dash. You can then either add or remove this marker from all of them.

The green indicator is set as the base color for Markers in the Global Setting.

And individually on the context menu with the right mouse button. See screenshots

I use those shortcuts exactly as you describe. Specifically during modeling, I need to quickly hide something, then reveal it. Occasionally, for example, when I need to hide an object in a scene because it gets in my way, just explicitly, for example, a narrow space, a neighboring house, I just need to hide it from a certain view, so I hide it individually in that camera. So more like this. And I set up some cameras like this, so sometimes I intentionally hide some things, but it’s always just a few things, it’s not many things that I hide this way in scenes. I usually control it according to markers or according to native tags on those scenes.

But the Hide and Unhide commands are one of the most used by me during modeling.

on the name change it is possible one of my other machines had it named differently, At work i have only one to check. Ill check the others tonight.

On the indicator thought. Clicking an arrow icon for the marker highlights those items in the model. And clicking a second mouse icon adds to the selections. At that point, to deselect, how do we know which mouse icon was selected, as all of the checkboxes will have a dash and no other indicator for which mouse icons were selected. If you guess the correct one it will deselect that group of markers, but clicking the wrong one will add to the selection group. I think on one of the beta versions the mouse icon actually changed color or had a colored background when selected. But on my version that area is rather small so if that function is still there its hard to see. A solid filled mouse icon might be more visible?

Bug with names:

It must be a bug probably after implementing Label Markers in combination with an older model that was created before this implementation. I edited the entries in Labels there. I will look into it and if this is the case, I will prepare a corrected version.

Please make a copy of the older model so we can compare whether the fixed version will do it again or not. If you still have the model, don’t save it again.

I’m not specifically making migration mechanisms for older models at this stage of development, as a few people are testing it so far and I didn’t want to “dirty” the code unnecessarily.

Selections:

Ah, I understand what you mean. Switch to my original SKIN - see screenshot. It works there.

I’ll fix it in the default ones so it works there too. Probably with some text color. The default skins came after my original ones at the request of people, so I still need to figure out these little things on them.

There it is. I was sure you had it before.

The color change is very subtle though, maybe a black filled mouse or solid white mouse might be a bit more noticeable. But glad you found it.

OK, I’ll play around with this and fine-tune it.

@mark.perrah

Beta 20:

1/ Improved Select buttons:

  • show active selection in all skins
  • enlarged and full solid icons

2/ “Marker name swapping” bug should be fixed - you can test it.

This looks excellent. Tested with a few skins. Just what I was hoping for. Thank you. I’ll test the re-naming issue tonight when I get home. My work computer pulled from the Trimble connect file, but I think I have a local copy on the mac mac mini. I’ll keep you posted. Love this update. Thank you

Not having issues with re-namimg going from beta 17 to beta 21 (its possible with 20, but its not a problem with 21) One thing i noticed different is the auto level created markers do not have a check box to apply object. Is this intentional? I tested beta 21 on Windows 11 pro SU26, Mac book Pro SU24 (2011 modified os), and Mac Mini SU25 (2012 modified os) all working and marker names were retained in update.

Automatically created level markers should not have a manual checkbox for using the object active. So yes - This is intentional. The checkbox itself should only be displayed so that you know where the selected object belongs and whether the automation correctly assigned it to the level.

{6E12216C-2A71-48AF-8DE6-CE3D4E6F4701}

Got to test the Match Markers tool. I was not sure how that worked. I thought I would be overwriting data. But without clicking it does show what I wanted. And I can hide rows or columns to see a specific portion. Very Cool! And if I do click to alter the selections marker it is non destructive. So I can refer to the Component definition to validate any unwanted changes.

{3AFA048D-4141-4948-BCE7-600F69C2CC7A}

I have been using 5D Auto Info tool. With his we can multiselect and see the label that shows on an overlay. For warehousing this is a dream come true. Yours has better control of visibility though. We can click on a single group header in his and all the group items get the label to show, but they need to work out layer order. Sometimes the dashed line of the selection ends up in front of a label. It is nice to have the object instance be the product at that location and we can filter to show only that.

{460890C8-0F41-4665-86FB-CCB5BEE36323}

{460890C8-0F41-4665-86FB-CCB5BEE36323}1920×1026 496 KB

It would be helpful to hide the unselected objects so the visibility of what you are looking for would be more accessible. Yours can do that easily. The ability to import the object instance data from selections would be ideal.

{21341BF5-C58D-4C83-B0D3-019392C15E5C}

See how much more visible locations are with your tool. But with labels like 5D has in front would be ideal

I’ll play with it. 5D+ Plus is a great plugin, I’m currently working on a synchronisation between 5D+ Plus and Liserok Level Markers. So that the user of both plugins doesn’t have to enter it twice in both interfaces. The first test version looks like this so far:

This looks amazing. Love the idea of not having to double enter. great idea.

Thanks to @jure for this. He came up with the idea :wink:

It’s really good like this if someone uses 5D+..

Just read another post regarding the cursor focus issue. It was a reported bug, fixed in 26.2.243, I am on 26.1.252 at work. And all my machines at home are 25 or lower as my hardware cant support newer. My company requires tech support to install updates lol. But I’ll request that to get that done shortly. Not sure if it was in earlier versions but I have several installed for testing. For win11 - 2024 and 2026, for mac - 2024 and 2025. Possibly getting an M2 Mac book this week end that might run 2026 for mac :slight_smile: