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

Hidden app window #113

Closed
BarbosaNath opened this issue Aug 24, 2021 · 4 comments
Closed

Hidden app window #113

BarbosaNath opened this issue Aug 24, 2021 · 4 comments
Labels

Comments

@BarbosaNath
Copy link

BarbosaNath commented Aug 24, 2021

I'll refer to "GDX Texture Packer GUI" as "GTPG"

Some days ago I got a strange glitch in my GDX Texture Packer GUI.

Every time I'd open the jar (or any other GTPG executable), nothing would show on screen, but it would show on the task bar and the task manager that the app was open.

When I tried to open it by the command line (java -jar) I got a warning that read something like this (I don't have the exact words anymore).

LibGDX 1.9.3 recommended to Vis UI version XXX, you're using LibGDX 1.9.2
Some things might not work

So I to got the source code to change the GDX version, but it was already up-to-date and the GTPG was still not working.

Finally, I gave up on the glitch and just downloaded an older version to see if it worked, and it worked just fine. So fine indeed that the newer version returned to work out of nowhere.

Don't know how the glitch was caused, don't know exactly what fixed it.
The only clue I have to the cause of the bug is that I might have turned off my computer without closing the app. Other than that, nothing comes to my mind.

Thought I already solved it, I was recommended to post this anyway so other people would know what to do

  • TL;DR App was open but hidden, open old version and it's fixed
@metaphore
Copy link
Member

Hi there, thanks for the extensive description!

I'd assume you're on Windows 10?
Judging by the description, it sounds to me that the issue is with the application window location being outside the screen.

When the app is being terminated, it memorizes the exact location (position + size) to restore it on the next startup. I think your assumption is right, the powering off the computer has that side effect on the window params persistence logic. Probably by the time the app tries to save the window state, the OS has already terminated some of the windowing services and the app receives wrong values.

I'll have a look and try to reproduce it. And I have a guess that from perspective of my code, there's very little I can control in such situation. So an obvious workaround would be to validate the last saved window location on startup and reset it in case something is wrong.

In meantime to help you fix your window, you might try one of these approaches
https://www.technipages.com/bring-off-screen-window-back-onto-screen

@metaphore metaphore added the bug label Aug 25, 2021
@BarbosaNath
Copy link
Author

I don't know if it's really a window out of the screen situation, when I was having this problem I tried that windows function to put every window in cascade and nothing showed up. I also tried the "win + arrow keys" shortcut, and nothing still.

metaphore added a commit that referenced this issue Sep 11, 2021
@metaphore
Copy link
Member

@Maikishiti could you please check if the problem persists for you in the 4.10.1 release?

@metaphore
Copy link
Member

Due to lack of new details, I guess the bug was fixed.
Feel free to reopen if the problem still stands.

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

No branches or pull requests

2 participants