|
|
can you u/l an example .sla to expedite this process for the team? thanks |
|
|
Can confirm the phenomena in 1.4.5 Not reproducible on 1.5.0 + currently building 1.5.1 so I can't test yet (on OSX 10.10.5) |
|
|
moving to 1.4.6 roadmap for craig and jean to decide |
|
|
AFAICT, this happens in 1.5svn, too the problem is that once you have set the bleeds there is no obvious way to set the gap between the page as they are rendered on screen. the internets are full of people asking for help on this topic... (of course, the main problem is that printers ask for bleed and users apply them without really knowing what it means and do not know what to do when images cross pages boundaries in a strange way....) |
|
|
I can confirm this is still an issue with 1.5.3svn - happens both on the screen but also in exported PDFs. It is not an issue of using bleed, but it can happen easier with bleed, because it does not count into the on-canvas page distance. An object will appear on another page in the exported PDF (but also exported image) depending on the Display/Scrach Space/Gaps Between Pages -- if it appears on another page on the canvas, it will be also exported that way. vsep-50mm.png (8,911 bytes) vsep-1in.png (10,461 bytes) |
|
|
Correction: I am using 1.5.4svn. |
|
|
My suggestion would be to ignore all page items for which PageItem::OwnPage!=pageBeingExported -- during both image and PDF export. Checking that objects from other pages don't stick out to other pages (because that would cause different on-screen and different exported output) might be added as pre-flight check, similar to objects out of page and such. |
|
|
This issue is still present in version 1.7.3. If you create a new document with a sufficiently large bleed, the bleed areas of adjacent pages overlap each other. If you open a file with bleed/slug while cropping to the MediaBox, it opens correctly and the spacing between pages is preserved. However, if you open the same file while cropping to a different page box, objects located in the bleed/slug area overlap between adjacent pages. A possible solution would be to always calculate the spacing between pages during import based on the MediaBox, or alternatively, not display objects that fall outside the selected viewing/cropping region. |
- Anonymous
