- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report
Hi,
I need to do specific things before exporting drawings to PDFs, some of which (one example: making sure the parts list is sorted the way it has to be) causes the drawing to need a full update on all views (that has balloons).
I've been using the built-in command "DrawingUpdateAllSheetsCmd" from the vba macro, with Execute2(True). This should make it synchronous and shouldn't give control back to the macro until it fully completes. And I haven't had problems with this before.
But now it doesn't work anymore, the command returns control to the macro even before the view computation is done, so the PDF will contain faint/badlooking bitmapped crap instead of the vectorized views. I dunno why is this now? Is this a new bug in the latest update?
Same thing happens if I do a Document.Update, or even if I go through all sheets and all views and update each one individually.
How can I make sure, views are done updating, before continuing with the macro? Is there any way except for checking running viewcompute threads?
Or does anyone know why this command is not synchrounous anymore even if it is executed as such?
Solved! Go to Solution.