With multiple pages. Say I am on page 1 and I move an object out of the printable area. Then I go to page 8. That object used to still be visible off to the side, and then I could move into page 8. But now when I move an object off to the side, off the printable area. It is not available when I go to another page. How do I change this?
In the settings for the Objects docker, there is a setting that is checked by default: "Keep Desktop Objects on Layer".
To have the page/desktop behavior of 2018 and earlier, that option needs to be unchecked.
Thank you for this info - I have just moved up to 2021 and that was making me crazy - either remembering to open the desktop layer or having to drag it down there when I'd forget. It seems that it would have been a handy thing for them to add in a "what's new" section, but I honestly also can't figure out a good use to do it this way either. LOL
Thanks for saving me infinite future time!
This feature was a result of Corel screwing up the fix that was needed because they screwed up the multiple page/multiple page size function.
So so called power users thought the current state was a good idea and advised Corel of such.
Previous behavior was wrong and had to be corrected.Problem was that objects outside the drawing area not only moved to a different layer, they could also be pushed to a new position when we switched page or saved the document, which could lead to objects disappearing out of sight.This happened automatically and could not be turned off, and could destroy the document.Desktop area is great for storing objects but these objects should never move without the user's knowledge.I agree that Corel could have been more clear about the change though, and why it was needed, and also how to enable the "feature" for those who need it.
These desktop objects moved because providing the multiple page/multiple page size feature the so called power users wanted was done incorrectly.
Then fixing that error was again done incorrectly, again a feature desired by so called power users. Resulting in the a$$ backward feature we now have and an object docker that is more than quite dysfunctional. My God, objects on the desktop need to be always listed as just that in the object docker.
All that ever needed done to fix the desktop objects moving was for the multiple page/multiple page size mode to lock the desktop during that mode of operation. DUH!
The entire process reminds me of reading Foster Coburns instructions in his books for using transparent drop shadows. A power user driven feature that was dysfunctional (nearly always having to be fixed at output) for I believe 9 cycles!
Yes this all was Corels fault but the core of the fault was their desire to give power users what they though they needed in a CHEAP way. Actually much like many Draw users.
Don't understand why you are so obsessed with power users?What is wrong with using a software's full potential, to quickly achieve the desired result in the fastest and easiest way possible?The multiple pages and pages of different size features have been in Draw for a long long time, and neither you nor I know the exact reason they were added. Blame the power users if you like but without them and Corel's urge to be ahead of its competitors at the time, we would still have a very rough and limited tool to work with. Stable perhaps, but very limited.
David Milisock said:All that ever needed done to fix the desktop objects moving was for the multiple page/multiple page size mode to lock the desktop during that mode of operation.
How do you mean?That objects shouldn't move to Desktop automatically if the document had pages of different size, but they should if all pages were the same size?
Ok this is for those who never grasp the problem.
When they enacted the multiple page/multiple page size feature they created the problem of objects on the desktop moving when the user moved from one page to another. I.E., an object on the desktop of a small page vs on object on the desktop of a large page. The desktop being defined as the area outside the assigned page size.
When they tried to repair the situation, they took and changed the way every user of CorelDRAW that used multiple pages worked and changed the default. BULL! It's listed on the forum regularly as an issue and the problem only existed for the multiple page/multiple page size user.
Keeping desktop objects on layer as it functions in the object docker is misnamed. It should be labeled keep desktop objects on layer AND PAGE because in the objects docker that's where you'll find the desktop objects in the docker, on the layer and in the page.
If I get a 35-page document in from a client and one page, say page 34 has something on the desktop I must page though the entire document either via the page display or hunt through how many thousands of objects in the objects docker page by page to find them. BULL! I still do not take in Native CorelDRAW files unless the keep desktop objects on layer has been disabled in the file before sending it to me.
How many cycles has this been an issue? 2019, 2020, 2021, 2021.5, 20922 2023 and now 2024. Can we count this as 6.5 cycles or just round it up to 7 cycles?
Regardless of operational mode, in the objects docker, desktop objects need to be in the desktop area of the docker and labeled for their layer and page. It makes them easy to find and is an intuitive/cost effective process. The lack of functionality is one of the reasons that CorelDRAW is considered unprofessional in the graphics world.
The core solution would have been to enact a process in an intuitive manner in terms of the docker and set Draw to use keep desktop objects on layer as the only mode for the multiple page/multiple page size workflow, letting all other users alone. It supports both user types in an intuitive manner.
For people who support native CorelDRAW files the entire process as it exists since version 2019 is a screwup waiting to happen at output.
The object docker since version 2019 continues to be a mess, especially when moving things to the desktop. In one mode it places desktop objects in the docker on the page but fails to label them as actually being on the desktop. Why is this important? Because the desktop can be huge in terms of physical size (well off the screen) making finding a problem item difficult, worse making it easy to miss.
In the other mode, objects that are moved to the desktop are not immediately registered as being on the desktop (as soon as you release the mouse) in the objects docker until you move to another page or some other obscure thing. WTF!! A Mickey Mouse operation if I've ever seen one! The concept is to improve something when it is rewritten, not to maintain dumb and dumber.
What problem do I have with power users? The concept is a BS term, no one person can use the application to its full potential for one. The other is that the power users tend to push for features that they like for themselves and forget how it affects most users.
The result is while Corel can produce the highest quality core technology output its lost nearly all its corporate appeal, damaging the value CorelDRAW users have to larger companies.
David Milisock said:I still do not take in Native CorelDRAW files unless the keep desktop objects on layer has been disabled in the file before sending it to me.
You still haven't realized that "Keep Desktop Objects on Layer" is a user setting, not a document setting.So if you prefer to have it disabled, simply disable it once and for all and you can accept any file.
David Milisock said:If I get a 35-page document in from a client and one page, say page 34 has something on the desktop I must page though the entire document either via the page display or hunt through how many thousands of objects in the objects docker page by page to find them.
If this should happen to me, I would (temporarily of course) disable "Keep Desktop Objects on Layer" and browse trough the pages with Page Down. All objects outside the drawing area would then jump to the Desktop layer. Problem solved in less than ten seconds.
David Milisock said:no one person can use the application to its full potential for one.
True. But learning how to use it as efficient as possible and take advantage of features and small gems, distinguishes the average user from a professional.Any change in an application will divide users into two categories; One that only sees a broken feature and another that tries to see how this change can be useful and enhance the workflow.