piskelapp / piskel

A simple web-based tool for Spriting and Pixel art.
http://piskelapp.com
Apache License 2.0
11.07k stars 770 forks source link

Confirm popups are invisible on Windows 10 desktop application #801

Open Ists-Cilveks opened 6 years ago

Ists-Cilveks commented 6 years ago

The piskel program crashes when i import images or just try to close the program. It's not really much of a crash: the program goes unfocused and gives error sound when I click, though nothing is lost. With image importing this happens with PNGs as single images and spritesheets. With closing whether with the button or alt+f4. Then, pressing f4 refocuses the program and everything works. To close the program i need the task manager. I'm using the newest version (downloaded today), though the same or similar things happened with 0.10.x. I'm on windows 10. The crashes don't seem to be affected by anything, like the images complexity. Everything seems to work on the website, to i have a resort :/

juliandescottes commented 6 years ago

Thanks for logging the issue! Both the scenarios you describe normally trigger the display of a prompt.

At the end of the import there is usually a prompt "are you sure you want to replace your sprite" and when closing the application with unsaved changes, there is a prompt about "unsaved changes".

For instance when I finish the import of an image here is what I get on OSX with the desktop application:

image

Do you see any message when completing the import? I am wondering if there could be a bug with win10 and prompts.

Ists-Cilveks commented 6 years ago

Alright, i found roughly what's going on. The screen generates, making everything else unclickable (with the error sound). There is a region in the middle of the browser (not necessarily the screen) which does not make the sounds. If you click a bunch, you can find the rough frame of the message and also the buttons (opposite order on windows). The mouse cursor doesn't change on the buttons. Screenshots: before crash and after with an outline of the message. screenshot 41 screenshot 42

juliandescottes commented 6 years ago

Thanks for the investigation! I'm guessing you are seeing this issue more often with v0.14.0 because the prompt at the end of the import step is a relatively recent addition.