-
Notifications
You must be signed in to change notification settings - Fork 18
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
Panel with window list kept active in bordered fullscreen mode (Cinnamon) #23
Comments
|
Setting window/size/fullscreen=true in project.godot fixes this for me on Linux Mint 20.1 with Cinnamon. I don't have any other system to test if this breaks for other systems. Side note/question: Does/should the burrito window (with the red border) scale with different resolutions? On my 2560x1440 display, the windows only occupies two thirds of the screen, which means the drawn paths are somewhat off (but usable) and the minimap overlay is totally off. Interestingly, setting window/size/resizable=true (with fullscreen=true) makes the burrito window scale somewhat, by which I mean that the paths are nice and central and the minimap is only a few pixels off. |
`[display] window/size/width=1820 it seems the window size is hardcoded in the project settings. maybe there should be a new issue about "attaching" to gw2 window? taco/blish get the window size from windows api and resize/reposition themselves to match the gw2 window. @TarEnethil @Sejsel are you guys using windowed full screen for gw2? #25 had issues with burrito going into background when clicking on gw2 window in kde, just wanted to check if cinnamon had the same issue. |
@coderedart I am using windowed full screen, yes. Burrito stays on top of gw2 regardless of the fullscreen=true. When I tab out of gw2 (gw2 window not minimized!) and click back into it, it doesnt actually focus gw2 but rather the burrito overlay, which means I must alt-tab into the game. |
@TarEnethil I did not get around to testing multiple screen resolutions in the original development. I play on a 1080p screen. My opinion is that burrito should cover the entire gw2 screen even if it is being played at a larger resolution. I think it makes sense to open a new issue for that. @coderedart That hardcoded value becoming dynamic sounds like good idea. It reminds me that in my setup any values close to 1080p were automatically expanded to 1080p, which is why those numbers are so awkward. If we are able to get the gw2 window position that would be great. I did run into some issues with positioning though with #8 . Not sure if those will effect attempts do do this. @TarEnethil Once you refocus and alt-tab into the game are you able to click on burrito normally or do you have to alt tab back to burrito to interact with it? Or does mouse focus work correctly? |
Will make one tomorrow if you haven't done so by then @AsherGlick I cannot interact with burrito when tabbed into the game. I indeed need to alt-tab into the burrito process, click the (slightly misaligned) icon, load a trailpack, close the menu and then alt-tab back into gw2. I guess this is a cinnamon-related issue, I don't know if something can be done about it here. |
Not just cinnamon, KDE has the same issue that input doesn't work properly with windowed full screen |
I have broken out the screen sizing issue into a separate thread #29 so we can return this bug to the original topic of incorrect window stacking. @Technetium1 make sure your burrito_link is running properly. #24 may help provide some insights into that. |
i think this issue and #25 are both related to stacking order of windowed fullscreen gw2 and the overlay. |
@Sejsel @Technetium1 With the pull of #39 the likely proposed causes of this issue have been addressed. Can you confirm if this continues to be an issue with the latest upstream build? |
@AsherGlick testing https://github.com/AsherGlick/Burrito/actions/runs/1332226605 with Running before game is open:
and nothing came up... Running with game open already
and nothing came up... Testing Running before game is open:
and nothing came up... Running with game open already
and nothing came up... |
@Technetium1 Can you explain what "nothing came up" means? Did the burrito window disappear when you started running the link code? Or is it still hidden behind the gw2 window. |
@AsherGlick Nothing changed whatsoever, there was not even a window I could move to the front anymore. Notice in my previous screenshot there is a burrito icon in the bottom middle, that window doesn't even seem to exist temporarily anymore. |
If you just launch Burrito without burrito_link do you get a window, it will just be the burrito icon? There is #40 that could be compressing it to a 1x1 pixel window as soon as it connects to burrito_link the first time. |
@AsherGlick I have a burrito icon, but a window/overlay is not visible. Might be related to # 40. 1st
2nd
3rd
|
These logs are very interesting. They seem to show that the two external dependency libraries are not being loaded, one for X11 settings and one for XML parsing. It looks like it is trying to load them from their build directories. I'm guessing there is some error in the CI code or export settings that is not bundling these files in. If you see the icon then the overlay is present. When clicking the icon that read border should appear as in your previous screenshots. If clicking the icon does not create the red border then it could be that the errors in your logs are causing the overlay to hang preventing any interaction. Unfortunately debugging that further may require a fix for the library loading first as that issue might be masking others. I have created #44 to track that issue. |
That issue has been resolved. |
I haven't tested this in a long time, it somehow slipped through my notifications and was forgotten about, I'll try it again soon. |
Burrito keeps the panel with window list active, which obscures a part of the game. This is sadly enough of an issue for me for this to be unusable. I am not sure if anything can be done about it on Burrito's side.
Burrito
No Burrito
The text was updated successfully, but these errors were encountered: