I see this when exporting to PDF.I compose with Snap to page yet something falls "outside". Wireframe view gives no clue and Print Preview is the same. So item by item I cut and paste objects to another page, test PDF export to search for the offending piece THAT'S ONLY A HAIR OFF. Time, time and more time playing a game.
Just need one guy in the coding chair to change the message to "I Spy on Page # that it contains objects that fall outside the page". Then it becomes fun .. is it the rectangle? No .. is it the image? No ... is it the border line? No .. is it the glow or drop shadow? No ... is the giraffe with sunglasses on?
NO! >>> JUST TELL ME WHAT IT IS IF YOU KNOW IT'S THERE!
This message drives me nuts and IMHO is inadequate and nothing more than Draw acknowledging a defect within itself as acceptable. Makes it very difficult for me to upgrade. I'm boycotting upgrades until objects that fall outside the page are identified or shown in some manner. Employers and clients only pay for production, not extravagant puzzle solving.
Thanks all for replying but I don't see that I can upload a file. Anyway, I'll be able to find the offending object myself, I don't need help with this. My main complaint is if CorelDraw *knows* objects fall outside the page, it should not keep it secret. Highlight the objects in Object Manager please.Also, there's a statement, "Details: Any parts of the object that fall outside the page will appear cropped in Acrobat Reader"This does not entirely happen. Maybe the object is unseen but the page size has increased to accommodate the secret unseen object.
So the way I play the I Spy Game is to make a second page. Item by item I cut and paste to the next page, try export to PDF until I get the dialogue bot to appear on the freshly pasted object. Grrrrr.
How do you feel about macros?
I wrote a small VBA macro to:
1. Tell the number of objects (on printable layers) that are not entirely within the page boundary.
2. Select those objects.
You're welcome to try it if you wish.
Mine shows which objects they are (by selecting them).
Mine does not take into account the "node handles" when figuring the extents of the objects. So, for the sample you provided, it reports that everything lies within the page boundaries. So, I consider it to be a way to tell when CorelDRAW is giving you a bogus warning.
As it is now, mine does not take into account outline widths (CorelDRAW doesn't take that into account, either; just uses "wireframe" information). I could write a version that does, though.
Maybe ask Corel if they would want to purchase it and incorporate it into their program. For me it's one of those nuances that stops me from upgrading too often.
BeachApe said:Maybe ask Corel if they would want to purchase it and incorporate it into their program. For me it's one of those nuances that stops me from upgrading too often.
This is one of many things that the Corel folks are certainly capable of doing if they wanted to. They aren't going to want to buy my dinky little VBA macro; they already know how to do this.
What I might like doesn't always qualify as a priority for them, so as an alternative to growing old waiting, I sometimes take a swing at doing it myself. By now, I have a substantial collection of homemade tools that suit particular needs.
With other programs/applications I use there are always guys like yourself. They too have a substantial collection of homemade tools that suit particular needs and set up a page selling them. What you do most likely has worth and people would be willing to browse through your menu of solutions and buy the ones suitable to their needs.Here's one such guy I'm familiar with as an example. http://www.mobirise-tutorials.com/
The little macro I mention is something I put together, for fun, after reading this thread. Before that, I was unaware of the "node handle can trigger the warning" thing (which I think is not very good behavior).
The "select the objects" part of that macro has its limitations, because it's possible to have situations in which some or all of those objects might not be selectable.
Like a lot of things, the simple case is straightforward...