-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
Full screen not working Mac OS X #50
Comments
Hi @Will2k! Thanks for coming here. Can you please tell me which OS your are using and send me a screenshot? Thanks! |
I can confirm the same on MacOS Sierra, appears to be fine on OSX El Capitan. I need to fix for a party in Sep, happy to debug with you. Ive enabled notifications for this issue so i can get you the info you need. Thanks for an incredible peice of software Joe! |
Thanks @pablocullen for helping me debugging this issue. Can you run checkout the latest code and run it from source. https://github.com/codingjoe/MusicBeam#contributing |
Sure, ill try this tonight and report back. I didn't get a notification about this in my email. Sorry for late reply. |
Ok @codingjoe it looks like this is coming back to the screen selection issue. When you start MusicBeam the stage always selects the macs internal screen (even if i set the primary screen to be the external one). If i implement the fix stated here: #40 (comment) then the correct screen is selected and the resolution set correctly. If i do not fix the code moving the stage to the external screen leaves it at the original horizontal resolution of the screen that it appears to start with, vertically it fills the screen though. This does look like its a framework issue. |
@pablocullen I believe this is a framework issue too :/ |
For anyone else having this issue, I found a simple fix. |
I can't get the app to work on full screen on my projector is covers 2/3 of the screen. Any news how to fix this.
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: