|
Is all of this about screen realestate limitations?
Why would hiding Preview behind a "tab" be useful otherwise?
FWIW, a "Preview" does not exist for every CodeView tab. When a CodeView Tab is clicked on and brought to the front, the single Preview window is loaded. Each Qt WebEngine window like Preview takes up a large amount of memory and requires many many threads (think how hungry for resources a Chrome browser is for each open tab). So a one to one between CV tabs and Preview can not be done. That is why PageEdit maps only the current page into a "Preview" and not a separate Preview tab for each xhtml chapter.
Also Clicking in Preview will sync CodeView and visa versa so they need to both be seeable at the same time to achieve that. And that can be very very useful.
So hiding one behind the other would never work for me or most users.
If the only benefit is screen size, have you thought about detaching Preview and placing it on a second monitor? Or if a second monitor does not exist, use a second virtual desktop where a single key is used to swap virtual desktops.
There are os level virtual desktops on Linux and Macs and I am sure Windows can most likely do something similar.
So please explain the benefit of hiding Preview if it is not screen realestate?
|