If I want to undo something, every part that was changed during undo action should be selected. Instead, almost every other part on my screen’s background are selected, including the ones from undo action.
That is really uncomfortable, especially when I’m working with 2 parts that are hard to select and then all the parts around it get selected as well…
Are you talking about when you undo something, some random part gets selected along with the undid selection?
I’ve been having this as well. It’s annoying.
Yep.
I’ve been tolerating it for too long…
Mostly I’ve noticed that when I Ctrl+Z I select a bunch of unions in my place. I’m not sure if I’m selecting anything other than unions though.
Same here.
I made a bug report about this a little while ago though it appears that it hasn’t been fixed yet.
It’s on our list to fix, we just haven’t gotten to this one yet. That said, I’ve upped the priority of this issue so we’ll get to it sooner.
Please, upper the priority even more
This is so much painful…
This is on our current TODO list and being actively worked on now. Hopefully we’ll have a fix soon.
What’s the current status on this bug?
This should be fixed in one of the next few releases.
Thank god
Paint.net has this feature, and its really useful
It would be nice if ROBLOX could have this in the future
you can basically scroll through your action history easier
Maybe make this it’s own studio feature request?
This is still an issue Silent137.
When you Undo an action with only 2 Parts of a multi-Part model selected it will select the entire model.
I miss the days when the Undo kept the SelectionBox just on the items you had selected and were working with.
It’s also a really annoying issue for me, slows me down a ton.
That alongside slow responses for selecting objects which leads to Studio recording a drag command on click need to be fixed.
Yeah, the lag I get when the place auto-saves can be a pain as well. Although the size of the place and the fact that I’ve got auto-save set for every 5 min. probably has something to do with that.
Ah, I see your problem now. The issue @EndorsedModel was having is now fixed. I’ll add yours to the bug list
Wait wait wait…
The issue of necessary selections was just added to the bug list? Do I understand correct?
Wasn’t it the topic of this thread already?