-
Notifications
You must be signed in to change notification settings - Fork 137
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
Moving mouse over Navigation Panel doesn't make it appear/highlight it until mouse stops moving #14
Comments
I actually can get the navpanel to show not when the mouse stops, but when it changes direction, is that the case? |
Sorry I haven't been around or responded since January. I had kidney stones in February which was only completely over with in June, also too much happening I needed to take care of, and currently notifications for github are on my alternate email which I don't look at often enough. To answer your question, first did you meant to say you can't instead of you can? Either way, when you change direction of the mouse you are first stopping the mouse for such a small amount of time that it isn't noticed. I tried changing direction and at first the navigation panel appeared, but if you shake the mouse back and forth to garuantee that it doesn't stop, then changing direction doesn't work. So the problem is that you must stop the mouse directly over the hidden navigation panel for it to appear WHICH IS DIFFICULT since it is hard to find the navigation panel since there is an empty space both above and below the navigation panel, which I would say is why it didn't work for you, so keep trying. This bug is the most annoying thing for me since it never gets easier to find the navigation panel to stop the mouse over it so it will appear. How it should work is as soon as the mouse moves over the hidden navigation panel, it should appear immediately even if the mouse is still moving. That way I can see when my mouse is over it since it will appear immediately. That is how I have always seen the onmouseover event work, at least with html webpages. Also I'm on Windows 10 now (previously Windows 7, but same computer) and am still using JpegView 1.0.40, but I will be updating JpegView shortly to see all the fixes you made which I had issues with, and within the next week or so I will respond to them to let you know how they work for me even though those issues are closed. |
I'm not a programmer, but I imagine this issue should have a simple quick fix for a mouse event, which I'm just guessing may possibly be in the file called GUIControls.cpp or GUIControls.h
Here is a list of the relevant changes I made to the JPEGView.ini file to help you more easily understand my explanation of this issue. These setting changes didn't create the issue, but it allowed me to noticed it since it is now very annoying.
(I set it to windowed mode, made it so the navigation panel disappears immediately as soon as the mouse isn't over it, made the navigation panel buttons 2x the size, and disabled the bottom panel popup.)
ShowFullScreen=false
DefaultWindowRect=sticky
ShowBottomPanel=false
BlendFactorNavPanel=0.0
ScaleFactorNavPanel=2.0
The issue is that the navigation panel doesn't appear when the mouse is over the navigation panel area until the mouse completely stops moving. It's very frustrating. The navigation panel disappears without an issue though.
You can see that this issue still exists even without my changes to the JPEGView.ini file, where in that case the mouse over the navigation panel doesn't highlight the navigation panel until the mouse stops moving. This still feels annoying.
The same thing also happens with the bottom panel popup (below the navigation panel) that is able to appear when the window is wide enough and the mouse moves over that area. I disabled this popup, so this will happen only without my changes to the JPEGView.ini file.
However, unlike when in windowed mode, it is interesting that when in full screen mode this problem only happens with the navigation panel, and not with the bottom panel popup below it. So there are 3 instances of this problem:
I would appreciate very much if you could find a way to fix this for your next release, whenever that will be.
The text was updated successfully, but these errors were encountered: