:VLR-objectModified Reactor triggers before objects in the database are write enabled

:VLR-objectModified Reactor triggers before objects in the database are write enabled

westonstout4413
Explorer Explorer
483 Views
1 Reply
Message 1 of 2

:VLR-objectModified Reactor triggers before objects in the database are write enabled

westonstout4413
Explorer
Explorer

Seems to be a bug, I would expect given the language of the AutoLISP documentation that :VLR-objectModified would trigger after all objects in the database have completed being modified and are write-enabled, but simply testing (vlax-write-enabled-p <VLA OBJECT>) on the entity which triggered the reactor inside the callback function returns nil. Additionally, running the below code

(progn (while (not (vlax-write-enabled-p <VLA OBJECT>))) (SOME_FUNC) ...)

Never returns true. I have a lot of objects I need to watch, and would prefer not to need to place separate object reactors on each one. My hope was that I'd be able to have one AcDb Reactor to manage changes to entities. As the objects never become write-enabled during the callback function, I cannot make meaningful changes to their data using functions like (VLAX-Invoke)

Am I SOL here?

0 Likes
Accepted solutions (1)
484 Views
1 Reply
Reply (1)
Message 2 of 2

westonstout4413
Explorer
Explorer
Accepted solution

Also the case with the docManager reactor :vlr-documentLockModeChanged, strangely.

0 Likes