I had posted this bug in another thread but it really deserves its own thread as it may be a separate bug. This occurs with Irfanview 4.10, on Windows XP 32bit.
Irfanview remains in memory when I hit escape in the following situation:
Have the following option selected:
[x] Start in full screen mode (if image loaded; single ESC for program exit)
When I hit ESC, it indeed closes the window...but the i_view32.exe process remains.
If you hit ESC the second time when this option is enabled, it will kill the process, even though the window isn't showing (once you click elsewhere, though, the ESC doesn't seem to get sent to the window). So basically you still have to hit ESC twice even with this setting, but the second ESC isn't obvious.
The first ESC hides the window, and the second ESC closes the process. Unfortunately the user has no idea the process is still in memory after the first ESC. Additionally, clicking somewhere else makes it impossible to do the second ESC, which means you have to resort to task manager. This behavior definitely seems like a bug since it creates a process with no window and no way to cleanly kill it.
-Dan
Irfanview remains in memory when I hit escape in the following situation:
Have the following option selected:
[x] Start in full screen mode (if image loaded; single ESC for program exit)
When I hit ESC, it indeed closes the window...but the i_view32.exe process remains.
If you hit ESC the second time when this option is enabled, it will kill the process, even though the window isn't showing (once you click elsewhere, though, the ESC doesn't seem to get sent to the window). So basically you still have to hit ESC twice even with this setting, but the second ESC isn't obvious.
The first ESC hides the window, and the second ESC closes the process. Unfortunately the user has no idea the process is still in memory after the first ESC. Additionally, clicking somewhere else makes it impossible to do the second ESC, which means you have to resort to task manager. This behavior definitely seems like a bug since it creates a process with no window and no way to cleanly kill it.
-Dan
Comment