ISOLATEOBJECTS to include the option to Lock, Freeze & VP Freeze

[Wish List System]

Summary: I want to be able to control the ISOLATEOBJECTS command behavior in the same way the similar Layer command does.

Description: When I run the ISOLATEOBJECTS command, it only makes remaining objects invisible, but they can be still moved, deleted,...etc if off-screen selection methods were used like: All, Previous, Last, Select Similar, Quick Select, & Object Selection Filters.

So I want the option to Lock or freeze these objects in the entire drawing or just the active Viewport.

Product and Feature: AutoCAD - Other

Submitted By: Tawfik Shehata on 10/27/2014

[BlackBox]

Summary: I want to be able to control the ISOLATEOBJECTS command behavior in the same way the similar Layer command does.

Description: When I run the ISOLATEOBJECTS command, it only makes remaining objects invisible, but they can be still moved, deleted,...etc if off-screen selection methods were used like: All, Previous, Last, Select Similar, Quick Select, & Object Selection Filters.

So I want the option to Lock or freeze these objects in the entire drawing or just the active Viewport.

Product and Feature: AutoCAD - Other

Submitted By: Tawfik Shehata on 10/27/2014

[Edit] - When you isolate one of multiple Objects on a Layer, that Layer is still unlocked (meaning all other entities on said Layer can be modified).

Why not instead use the LAYISO Command, as it also allows for Lock & Fade?

Example:

(command "._layiso" "_s" "_l" "")

[tawfik72]

For the very same reason the option to hide and isolate by object has been introduced while doing this by layer was already available. It's for when you need to exclusively work with only some of a layer(s) contents.

[BlackBox]

I we'll understand the issue; what I'm saying is there's no easy way to achieve what you're after.

What Autodesk will need to do is implement a DocumentLockModeChanged event handler that filters for the ISOLATEOBJECTS Command, in which case an ObjectModified event handler is registered that will track each Object who's Visible Property is being set to false, store the ObjectId to (static?) Field. This will allow the necessary infrastructure to 'undo' changes made to those invisible Objects, but still will not preclude them from being modified in the first place.

Knowing this issue exists, you're far better served to simply avoid the specific tasks you've identified here... If you know an a Object is part of your 'last' then don't use last as a command option... The whole point of setting Visible Property to false (isolating those set to true), is that they're not selectable. LISP selection sets, last command modifiers, and the like don't preclude Visible == false (unless you add the necessary custom code to do that), only locked layers.

Cheers