TheBard Posted April 1, 2018 Share Posted April 1, 2018 (edited) I'm wasn't quite sure how to describe this and I can't seem to capture everything in a screenshot. When entering Reading Mode with the window maximized for half a second it shows the windows as if it was no longer in maximized (as if you un-maximized it) and shows whatever else would be viewable if you did this. For example, it shows a smaller Accordance window on top of my internet browser. Then for half a second it shows the window maximized again, however now it shows it as if part of it has been moved up a bit with the top part cut off (I'm not sure how to describe it so see the screenshot). Then after the half second, it goes into Reading Mode as normal. When exiting reading mode it does the same thing it seems, but in reverse. So in short, it shows a bunch of odd windows and then finally goes to where it should and then does the same thing when exiting.. I didn't notice this in the latest version of v11 before I upgraded to v12 yesterday. It seemed pretty flawless. Not sure if this is technically a bug, but it looks kinda bad when switching and a little annoying, but able to live with. This is on a Windows 7 machine with 8GB of RAM, i3 processor, HP laptop. Accordance is the latest version of 12. v12.2.4. Edited April 1, 2018 by TheBard Link to comment Share on other sites More sharing options...
Orly Margolis Posted April 2, 2018 Share Posted April 2, 2018 I see what you are saying. This behavior has been there all along. It may be that because of font resource problem that was introduced in 12.2.4, switching to reading mode was always a flicker, and is now a slow full few seconds event. The font resource problem is fixed and is now being tested. You should see the reading mode back to what it always was in the next release. Thank you for reporting this problem. Link to comment Share on other sites More sharing options...
TheBard Posted April 2, 2018 Author Share Posted April 2, 2018 I see what you are saying. This behavior has been there all along. It may be that because of font resource problem that was introduced in 12.2.4, switching to reading mode was always a flicker, and is now a slow full few seconds event. The font resource problem is fixed and is now being tested. You should see the reading mode back to what it always was in the next release. Thank you for reporting this problem. That's great thanks for the update! Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now