|
|
generally speaking, i don't like the idea of automatically exiting a mode... i fear code complexity and other bugs showing up in the future... |
|
|
Maybe you could try the steps so as to understand what this report is about ? Scribus allready (automaticaly) exits the normal edit mode when the user clicks on a preflight checker's line that points toward a faulty element in a masterpage : it enters the masterpage edit mode that enables to fix the issue. Later on, when clicking on another preflight checker's line, scribus will (automaticaly) exit the masterpage mode and go to whatever mode is required to fix the new issue. Later on again, clicking on the "Ignore" button, or on the "Preflight Check again" should just (automaticaly) restore the initial state = scribus state when the PDF export was first requested = normal page edit mode. |
|
|
the more i read about it, and the more i think that the only good solution is fixing the PDF export and get it to also to work if by chance the cursor happens to be in master page edit mode. not by adding more checks, just by getting it right :-) |
|
|
MasterPagePDF.gif (833,093 bytes) |
|
|
Tested Scribus 1.5.3svn I can reproduce this. |
- Anonymous
