Quote:
Originally Posted by KevinH
Again, Sigil 2.5.0 had a bug that made it incorrectly sync to the top of file. That is why you saw your error messages more in Sigil 2.5.0. Please try the exact same test in the exact same epub on Sigil 2.4.2. It should act like Sigil 2.5.1, not Sigil 2.5.0 when it comes to syncing behaviour as that is the code we reverted to.
If Sigil 2.4.2 somehow syncs to the error message at the top, please let me know and I will try to look into what else changed between Sigil 2.4.2 and Sigil 2.5.1 that might change the behaviour. Unfortunately since 2.4.2 there has been a large number of changes, even Qt changes that could be a culprit.
Nothing from the Sigil 2.5.0 to Sigil 2.5.1 other than the reverted whitespace to top fix) should have impacted that behaviour (same Qt, etc)
|
OK. I tried on Windows with 2.3.1 (which I had available) and I downloaded 2.4.2. Both those versions behave as I remember Sigil always behaving and NOT as 2.5.1 behaves. This behaviour is not epub dependent and is same with both epub2 and epub3.
2.3.1 & 2.4.2: when I damage a tag in the lower half of a lengthy xhtml file, the PV pane immediately zaps to the top of the page and displays a red error warning. The amount of the page displayed in PV is just what it can get in the space available.
There is no attempt to sync with the actual error in CV - (and I never claimed there was). That is the way I have always remembered Sigil working over all the past versions.
2.5.1 doesn't display the red error message in PV if you are editing below the scope of what it can display from the top of the file. A user has no way to know an error message has been displayed if he is working further down in the file (unless, as I said, he damages the </body> tag).
2.5.1 on the other hand, maintains the sync between PV and CV right down to the place where the error is BUT this prevents the user from seeing any warning message. The warning message has been generated and becomes visible ONLY if the user scrolls to the top of the file in PV or just happens to be editing in the upper part of the file - near the top.
If an error message is to be of use, it must be displayed visibly. PV should NOT sync with CV unless the error message can be made to float over PV and not be displayed at its head. It was always displayed, IIRC, in previous versions. This change has happened in 2.5.1.