-
Notifications
You must be signed in to change notification settings - Fork 346
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Size of the built-in PDF viewer panel will be reset after restarting TexStudio #3749
Comments
If I remember correctly, the built-in viewer used to remember its width, so this seems to be a bug. |
I see that txs remembers width on linux. |
You're right. It worked correctly in the previous version (4.7.3). |
I don't see an issue on win11 with 4.8.2alpha4. |
Are you maximized? It does remember the panel size when not maximized, but when maximized the built-in PDF viewer panel size is reset. |
what is your monitor set-up ? |
1920×1080 |
I always use txs maximised, so I don’t know what happens when it is not. My set-up is 3840×2160 150% on one machine and 2×2560×1440 (100%?) on another machine. |
I still have the problem. downloaded the latest update 4.8.4 Does andybody has a solution to fix? its really annoying ;)
what do you mean by maximising the panel? its embedded and not a single window? |
I can confirm for a standard setup: Have a look at following screenshots. I used a tool which shows the current mouse pointer coordinates which I moved over the black line separating the editor part from the viewer part (the circel shows a large zoom around the mouse pointer). The main observation is that after closing txs, the black line is generally slightly shifted sideways the next time txs is started, even if the line was not touched beforehand. |
The panel size of the built-in PDF viewer will be reset every time I restart the TexStudio. It doesn't remember the size after I changed it.
Environment
Expected behavior
The panel size of the built-in PDF viewer will remember the size after I change it.
The text was updated successfully, but these errors were encountered: