The renaming of Groups selected in Outliner is insane

Hi Colin,

Thanks for looking into this. I have no clue why it isn’t bugging on your windows machine. At mine it fails every time I test it. See gifs. Shift-click, control-click - always fails once something is added from the Outliner. I think it failed a few times as well when only adding from the viewport but I don’t have a recording of that and I can’t reproduce it now.
Edit: in third video it also fails when only selecting objects in the Outliner

SketchUp 23.0.419
Windows 10 Pro 10.0.19045 (with latest updates)
select
select2
select3

I can replicate the issue with .419 on win 11.

I too am having this problem, have tried reinstallling and deleting cache files still same

Unfortunately this doesn’t work in my workflow either

How long until we get this fixed it seems anyone using the outliner is in limbo at the mo

How can we get sketchup to fix this quickly so we can go back to work.

I updated .net framework and even moved to windows 11 and no difference.

Hello I have still this bug on my 2023 version. Do you know when it will be fixed because it is completely annoying and make this version definitively unusable !!!

It took a long time to make a model where the problem happens every time. I did manage that recently, so now at least developers can know if any changes they make are actually helping.

Hope this helps!

1 Like

Strange but nice find. For users who use a Outliner based workflow and who name every group and component, temporary hiding/collapsing the EntityInfoDialog when you want to select something is really crippling the workflow.

I prefer to stick to SU 2022 until this is fixed - hoping in the new SU 2024 that comes sometime soon™

1 Like

Any other updates on this? its still happening for me on 23.1.340 windows

no update - hasn’t been fixed in any of 2023’s updates. Crossing fingers it will be in SU 2024.0 whenever that drops.

So far i have not noticed group renaming in 2024. crossing my fingers this is finally resolved.

I’m hoping that something was fixed, but when I went back to confirm that I couldn’t make the problem happen in 2023 either.

it does seem like a windows handle issue, maybe installing 2024 updated something that effects all installs?