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

Support second monitor + larger resolutions #528

Open
wcko87 opened this issue May 10, 2020 · 3 comments
Open

Support second monitor + larger resolutions #528

wcko87 opened this issue May 10, 2020 · 3 comments

Comments

@wcko87
Copy link
Contributor

wcko87 commented May 10, 2020

This may be related to issue #49

Some people use 2 monitors with different screen resolutions.
But there are 2 issues:

Issue A. beatoraja takes resolution information from the first monitor, which may be small.

So if the first monitor is 1366x768, but the second monitor is 1920x1080, it is not possible to run beatoraja at 1920x1080.

I think there are 2 solutions for this:

  1. Detect all monitors for resolution settings OR
  2. Allow all resolution settings, independent of detected monitor. (or allow custom resolutions like Custom resolution #49)

I think solution 2 is better.

Issue B. There is no option to select which monitor to use for full screen mode.

So beatoraja will always run full screen on the first (smaller) monitor.

@SackMagiclight
Copy link
Contributor

SackMagiclight commented May 10, 2020

beatoraja is implemented using libGDX (backend: LWJGL2).

LWJGL2 does not support multiple monitors.
LWJGL3 can be used as a backend, but it is in development and unstable.
(Also, backend changes make a big change to the program.)

  1. Allow all resolution settings, independent of detected monitor. (or allow custom resolutions like Custom resolution #49)

solution 2 is better.

Yeah. I think so, too.
I think that's the only way to do it.

@asesidaa
Copy link

Now that LWJGL3 has become the default for libgdx and LWJGL2 has become legacy, I think it's time to migrate to LWJGL3. I have experimented a little bit, and there are not much to change.

Aside from change the configuration and application type and some setter usage, the only real change is that in the main controller we need to change the Mouse.setGrabbed to some glfw alternative. You can check my experiment result in my fork.

@Pr0pHesyer
Copy link

Same issue.
Beatoraja always play in the main monitor set in Windows 11 setting.I need it play in hte 2nd monitor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants