-
Notifications
You must be signed in to change notification settings - Fork 350
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
Mouse cursor will disappear after double click the pdf viewer #31
Comments
which OS ? which version of txs ? |
TeXstudio 2.12.6 (hg 6632:7777b2b8a906) windows10 version 1709 |
I assume that you are using the windowed pdf viewer from txs ? |
Exactly! By the way, I upgrade the txs recently, and the previous version does not have the bug. I can not remember the previous version number exactly. |
I am experiencing the exact same problem. My temporary solution is to click on the "Scroll" button (hand icon) in the pdf viewer. |
Same issue for me. But it also appears when the Viewer is docked. TeXstudio 2.12.8 (hg 2.12.8-1-g68cd350) Windows 7 |
I am also having this issue... docked or windowed. Windows 10 |
Same issue here, TeXstudio 2.12.8 (hg 2.12.8-1-g68cd350) on windows 10. |
the same issue for me. it appears when the Viewer is docked. Windows 10 (1703) |
Same here. Happens also when the viewer is floating. Windows 10 (1803) |
Still exists with Windows 10.0.17134 Qt 5.12.1 and TexStudio 2.12.16 |
This bug does not show up on Linux. Tested with
Could you please merge the messages in this ticket? I suggest to add |
Happens to me on: |
Same bug for me TeXstudio 2.12.4, Qt Version 5.6.2 (compile Qt 5.6.2 R), Win 10. My current workaround: ESC (closes the viewer), then F7 (opens it again). |
Bug still present in Linux variant.
The workaround suggested by @rdecharette is what I am working with for now. |
I found a way to reproduce a similar state using 3.1.2 on linux. Steps to reproduce:
Two issues come to mind:
none of the reporters mentioned presentation mode being needed to trigger this, but this is probably pretty near the mark. If you set It might be worth asking the others to report the value of |
I think I have found a solution, please check latest version |
works for me, but previous reporters described different symptoms to my case - there may be more than one bug. I suggest you confirm with others before closing. Presentation mode has a cursor now, that's a significant change. I personally have no preference either way. I've never used it. |
with the new commit, I find that when first starting presentation mode, double clicking for the magnifier and than dragging it, the "scroll" cursor appears in the middle of the magnifier. If you release and try again, it happens again.. If you release and try a third time, no cursor appears. I don't think the fix addressed the real problems with the code. |
I don't see anything fault, screencast ? |
Could reproduce reliably yesterday, after recompiling, but I can't get it today. I'll see if it pops up again in the next few days. Different issue: on a multi-page document in presentation mode, can you trigger the magnifier with a double-click without the first click triggering a "next page" action? |
It seems not to be possible to separate click/double click events. I would actually disable the zoom in presentation mode, if nobody objects. |
That seems unlikely. I have no opinion on removing double-click-to-zoom, except that if activating it flips the page - it's useless. |
Hello, OS : Windows 10 TeXstudio 3.1.1 (git 3.1.1) |
@Remi-Boutin, can you check and report the value of |
Thanks JonathanLevine657 . Mine is |
try to use 3.1.2beta |
Thanks @Remi-Boutin, that's consistent with what I thought triggers this bug. As sunderme said, there's a fix for this already committed, which will be in the next minor version (currently in beta). |
The fix seems to do it ! Thanks guys, appreciate it ! |
Hello, usually I will double-click the pdf viewer and a magnifying glass will appear. After that, the mouse cursor will disappear. Close the pdf viewer and reopen it will solve this problem. But it is inconvenient.
The text was updated successfully, but these errors were encountered: