Skip to content
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

No Buttons shown at Commands & Preferences @ 13,3" display, 150% size #2299

Closed
greg4b opened this issue Mar 15, 2023 · 5 comments · Fixed by #2332
Closed

No Buttons shown at Commands & Preferences @ 13,3" display, 150% size #2299

greg4b opened this issue Mar 15, 2023 · 5 comments · Fixed by #2332
Labels

Comments

@greg4b
Copy link

greg4b commented Mar 15, 2023

Describe the bug
The dialog boxes for

  • Commands
  • Preferences
    is too big - the buttons for saving etc. in the bottom cannot be accessed.
    Display 13,3", 150%scale, HD Resolution

To Reproduce
open Commands or Preferences dialog box.

Expected behavior
Buttons in the bottom can be viewed and used.

Screenshots
See screenshot

Version, OS and Environment

  • Application Version 6.3.2
  • OS Win10

CopyQ FSDafo
grafik

@greg4b greg4b added the bug label Mar 15, 2023
@greg4b
Copy link
Author

greg4b commented Mar 15, 2023

Furthermore when dragging screenshot from Images tab - a second image is inserted... Advise? Thanks

@hluk
Copy link
Owner

hluk commented Apr 17, 2023

Furthermore when dragging screenshot from Images tab - a second image is inserted... Advise? Thanks

This has been fixed in 7.0.0 (#2304).

I can look into the size problem. It seems that some widget has some large minimal size configured.

@hluk
Copy link
Owner

hluk commented Apr 17, 2023

Can you check if it is fixed with this development build?

@greg4b
Copy link
Author

greg4b commented Apr 18, 2023

Hello Lukas,

Thank You - works fine! See screenshot:
CopyQ ehPJEl

Tried your development build 7.0.0-19-gfffaa3e1 on W10 (1920x1080) on 13,3" (HP 830G6)

@hluk
Copy link
Owner

hluk commented Apr 18, 2023

Thanks for testing. I will include the fix in the next version.

hluk added a commit that referenced this issue Apr 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants