Is it possible to downgrade from X5 to X3 using the X5 license?
The main reason is that I work on a lot of documents with 20-30 pages with many layers and when I need to hide layers I have to surf on each page to do that.
I found a macro, but it only toggles visibilitiy/print/edit on all pages, it is not a solution, because it may be some pages which I edited and changed the property of some layers only on that page.
I need to hide/disable layers when I publish to pdf. After, I have to go and enable those layers I need for final output (eps, ai and so on) and I have to go again on all 30 pages to enable or disable (depending on what I need).
And there are more reasons....
... I work with CorelDraw since CorelDraw4, in the 90's, but this layer issue is the most counter-productive thing ever.
I would like an answer from a Corel official, since I tryied to contact Corel support but I did not succed on their webpage.
Thanks,
Mad Max
I can surely understand what you say. I have stopped using Versions later X4 for my jobs with complex layers.
Mad Max said:I found a macro, but it only toggles visibilitiy/print/edit on all pages, it is not a solution, because it may be some pages which I edited and changed the property of some layers only on that page.
I am not a Corel official but thought this could help you. AFAIK, you can downgrade upto one version with permissions from Corel if you hold a valid maintenance subscription. This could be different in your region. Not sure. Hope you get an official answer from Corel here.
Mad Max said:Is it possible to downgrade from X5 to X3 using the X5 license?
Hi Anand
I m surprised to hear that u'hv stopped using X5 for so called 'complicated jobs'.
I remember u used to be someone who kept telling me the that X5 has the best memory management and it is so far the most stable version corel has ever released.
But thats not the case anymore and I was the first to say that, but everyone disagreed on the issues I raised here.
Now, u all have admitted that X5 has very serious memory issues and I hope these will be fixed in the next version.