-
-
Notifications
You must be signed in to change notification settings - Fork 139
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
NavBar Behavior #10
Comments
Yes, indeed. Thanks. |
Hello Yaron, This is fixed in master branch. NavBar can be further optimized but that is another matter. BR |
Hello Pavel, Great. Thank you. I really don't know how the NavBar should work and display the overall diffs. Best regards. |
Hello Yaron, Yes, there are still some issues. I'll check that. BR |
Thank you Pavel. I appreciate it. BR |
Hello Yaron, One a bit "strange" question - What is the resolution of your monitor? The current NavBar looks exactly as the first image from Doutei if you have a vertical resolution greater than the number of lines in the compared documents (the bigger number from the two). BR |
Hello Pavel, Thank you for everything. My resolution is 1360x768. The "Select First" is a truly brilliant idea. I'll elaborate on that and other issues. Best regards. |
Hello Yaron, Don't worry, we'll discuss things further when you have time, thanks.
I see what you mean. That's interesting but I think it might get a bit confusing for the user and it will add another compare command to the plugin menu (which seems a bit too much). BR |
Hello Pavel, Some screenshots of the NavBar on my machine. Thank you. BR |
Thank you, I'll investigate it sometime in the future. BR |
Great. Thank you. BR |
Hello Yaron, I've made a lot of modifications and optimizations to the NavBar and basically it should be functional and working OK now. There might still be some issues but nothing critical I hope. I'll clean them regularly as those pop-up, thanks. BR |
Hello Pavel, As you know I hardly use the NavBar. Thank you very much. |
Thanks Yaron. BR |
I think it's good to have a reference to this issue.
The text was updated successfully, but these errors were encountered: