Is there a macro that would seek out all symbols in a document and revert them all to objects? I believe the symbols are really bogging down my file and there are too many at this point to find them. Thanks.
Are these supposed to jump to each page?
no only on current page
for all pages on active document try code below
Sub RevertSymbolsToObjects()Dim sh As ShapeRange, s As Shape, dp As PageActiveDocument.BeginCommandGroup ("RevertToOjects")For Each dp In ActiveDocument.Pagesdp.ActivateSet sh = ActivePage.Shapes.FindShapes(Type:=cdrSymbolShape)For Each s In shs.Symbol.RevertToShapesNext sNext dpActiveDocument.EndCommandGroupEnd Sub
I guess I am wondering - even aside from automation - why the reverting of symbols to regular shapes is so slow.
Any chance that this is some of the nasty AMD video card / Windows 10 Creators Update performance problems some users have experienced with CorelDRAW?
I know that some of your information is proprietary. Could you share one of the symbols that takes ~5 minutes to revert?
If you create a new symbol - something simple - then is that also very slow to revert?
Try this. My document isn't any better.
drive.google.com/open
It seems to me that the memory use goes up, up, up when one reverts symbols.
Opening a file with those 31 symbols in it, Task Manager showed 0.27 GB for memory.
After manually (no VBA macro) reverting those symbols, the Task Manager was showing 2.29 GB.
It seems to be even more dramatic when doing it with the VBA macro. I set up a 100-page document with 310 of those symbols distributed through it, and it maxed out the 16 GB of physical memory I have on the machine I'm using.
I DID get that document to process all the way through by setting up the macro so that it would:
until all pages of the document had been processed. Closing / reopening frees up some of the memory that has been used.
I'm traveling right now but had to reply. I find this really fascinating. Why would symbols cause such a drain?
ruckstande said:Why would symbols cause such a drain?
Perhaps some part of the reversion process uses memory, but is not releasing it when it is no longer needed.
That's just me guessing; it would be great to have the Corel devs take a close look at it. I am not holding my breath!