Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Problems with the interface in high resolution #10

Closed
ewilded opened this issue Oct 4, 2016 · 10 comments
Closed

Problems with the interface in high resolution #10

ewilded opened this issue Oct 4, 2016 · 10 comments
Labels

Comments

@ewilded
Copy link

ewilded commented Oct 4, 2016

I noticed that when using Autorize in high resolution (like 4k), the entire configuration interface elements overlap each other, rendering it useless.
autorize
Please see the screenshot.

@Quitten
Copy link
Owner

Quitten commented Oct 4, 2016

Hi Julian,
Thank you for reporting this problem, however due to a lack of time I will not be able to fix this in the near future. Possibly my partner, Federico will be able to take care of it.
In any case, if you would like you could fix the relevant code parts yourself and send the pull request I will gladly accept it.
Let me know whether you prefer to wait or to fix it yourself,
Kind regards,
Barak

@ewilded
Copy link
Author

ewilded commented Oct 5, 2016

To be honest I prefer to wait (:D), especially as I am terrible at Java and UI... Nonetheless I think I can give it a try. I have already achieved some improvement, will try to make everything look fine - then I will test in low resolution and make a pull request.
Regards, Julian

@Quitten
Copy link
Owner

Quitten commented Oct 5, 2016

You can give a try and i will perform tests on the pull request

ewilded pushed a commit to ewilded/Autorize that referenced this issue Oct 7, 2016
Changed layout control in order to get rid of issues with high resolution screens (Quitten#10).
Now it looks fine under 4k, did not test with low resolution.
@ewilded
Copy link
Author

ewilded commented Oct 7, 2016

Allright, here it is ewilded@3c51397#diff-370c88cf0195bbc74583252c05ef49bc.
Does not look so bad under my 4k now, however I am not sure if I did not break low resolutions in turn ;) Anyway, the root cause was using absolute positions and sizes instead of features offered by layouts.
If you are fine with my changes, please let me know, I will create a pull request.
Regards,
Julian

@ewilded
Copy link
Author

ewilded commented Oct 7, 2016

Ok, before you actually make a pull request - I just noticed that somehow my changes broke the automatic interception (with the default 'in scope' filter), so far I have no idea how. I will let you know as soon as it's fixed.
Thanks, Julian

@Quitten
Copy link
Owner

Quitten commented Oct 12, 2016

Ok, waiting for the pull request.

@Quitten
Copy link
Owner

Quitten commented Oct 12, 2016

Hi Julian,
i just tested your code and i saw that it changed the entire UI of the plugin, i would like to solve the resolution problem without changing the UI itself, i thought about checking the monitor resolution in the first initialization then adjust the buttons for it.
In case you can do that it will be great, because i dont want to change the plugin's UI.

@Quitten Quitten added the bug label Jan 17, 2018
Quitten pushed a commit that referenced this issue Jan 9, 2023
Autorize upgrade - Version 1.5
@ldionmarcil
Copy link

Ran into this today, made the extension quite unusable. Because all the Java GUI components are hard coded, there is no easy way to fix this. I spent some time rewriting the indices to make things a little more readable. Forked this because its not a systemic fix, but a very dirty workaround.
Before:
image
After:
image

see ldionmarcil@e85d884

Quitten added a commit that referenced this issue Jul 27, 2024
@Quitten
Copy link
Owner

Quitten commented Jul 27, 2024

Hey @ewilded @ldionmarcil,
After 8 years :D, I found few weekends to implement GroupLayout on all panels (see commit 7856089), so this should be fixed now :)
Please let me know if it is fixed the resolution issue, so Ill close this issue.

@Quitten
Copy link
Owner

Quitten commented Jul 28, 2024

OK, so after 8 years, happy to say: closed.

@Quitten Quitten closed this as completed Jul 28, 2024
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants