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

Visual Bug: Dev Menus don't fit in screen #969

Open
HBIDamian opened this issue Apr 19, 2024 · 2 comments
Open

Visual Bug: Dev Menus don't fit in screen #969

HBIDamian opened this issue Apr 19, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@HBIDamian
Copy link

Describe the bug
Dev Menu doesn't fit to screen and continues off screen.
(Also causes "About" copyright to be occasionally hidden behind the About Menu Buttons.

To Reproduce
Steps to reproduce the behavior:

  1. Go on the launcher
  2. Click Settings
  3. Click Dev
  4. Resize the window in any way
  5. (Optional:) Click About

Expected behavior
Menu and content to fit in the screen.

Screenshots
If applicable, add screenshots to help explain your problem.
image
image
image

Desktop (please complete the following information):

  • Device: MacBook Air (M1, 2020)
  • OS: macOS (Version 14.4.1 (23E224))
  • Version: v0.14.0-macOS-x86_64-0.2.463 (build 463)
  • Installation Type: dmg

Additional context

  • It also happened on the Storage menu, but I'm struggling to reproduce it.
  • Too small of a window then moving to a different tab also causes the "Close" Button at the bottom to be completely hidden.
@HBIDamian HBIDamian added the bug Something isn't working label Apr 19, 2024
@ChristopherHX
Copy link
Member

ChristopherHX commented Apr 19, 2024

The visual UI is changing, the nightly looks really different https://github.com/minecraft-linux/mcpelauncher-manifest/releases/tag/nightly

image

Actually I still have the opinion that this specfic tab should not be used by people not developing the launcher.

@HBIDamian
Copy link
Author

UI looks snazzy! I like it! :D
If you intend for the general public to not use it, I suggest keeping it but keeping it under "Expert"/"Advanced" mode that they'd need to enable before using it. That way it's "Out of the way", and people who know what they're doing (or people who want to break stuff or test stuff) can use it.
One way could be discord's settings.json file that has DANGEROUS_ENABLE_DEVTOOLS_ONLY_ENABLE_IF_YOU_KNOW_WHAT_YOURE_DOING:true, option.
This idea kind of meets half way.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants