New XRef Layers Not Detected with VLISP
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hello all,
I'm coming across an "issue" I've not managed to come across over the last several years and looking for some general support or re-education on some nuances regarding the XRef updating/reloading process. Let me explain my scenario first:
There is a LSP utility I constructed that allows users to specify what layers they'd like to batch edit through a list of DWG files. This LSP uses VLlisp and calls upon the ObjectDBX shell to maximize efficiency. However, we just came across an issue where we add a layer to the base XRef file and the routine does not recognize the new layer in the DWGs with the nested XRef UNTIL we open all necessary drawings, just save them all, and close.
This gives me the impression that the drawings which has the XRef nested within it does not update the layer library/class (apologies for any improper technical lingo here) until a DWG is fully opened. Can anyone confirm this suspicion for me? Does anyone know of a work around WHILE utilizing the ObjectDBX shell?
At this moment, I'm thinking I just need to add a simple open in "foreground" or "background" option for users in such scenarios. But, would obviously love to keep this LSP to a 100% background function to speed through hundreds of drawings in minute or two. (Not saying we need to run this on hundreds of drawings! No, no. Simply testing revealed it could run hundreds of drawings that quickly is all.)
Thanks all for your support in advance!