#47 JPEGView Window Focus

[Max]

JPEGView not pics focus on their main window in some times.
Run JPEGView and instantly change focus to any other window = JPEGView will be opened in "background", without focusing and without addition in TaskBar.
So, would be great if window of JPEGView pics focus on yourself when it created (opened).

[David Kleiner]

JPEGView does nothing special with the focus. Normally Windows gives focus to the application that starts. If an application tries to force focus to itself, since many Windows version this call is simply ignored by the OS and the icon in the taskbar is blinking instead.
If you click immediately after starting JPEGView in another application's area, Windows seems to interpret that you want to focus there and thus does not give focus to the starting application anymore. I assume in most cases that is what you actually want - why would you click there otherwise?
The missing addition to the taskbar cannot be reproduced with 1.0.33.1 (the non-focusing can - but that is as expected, see above)

David

[Max]

Run some other applications = they are apply focus on yourself and it's okay.
Default Windows 7 Image Viewer, browsers, etc., even calculator.
Exclusions: some pop-up windows, like chats in IM Messengers, and it's reasonably.

About "missing addition to the taskbar":
Maybe it's depends by Window theme style? I use Classic (Windows 7). And JPEGView adds to taskbar only when their window got focus.

[David Kleiner]

I let Windows apply focus on startup, I won't change anything in this area, i.e. I will not force a Focus() call after startup.
I have never had any problems with that as long as I don't give focus manually somewhere else and in this case I don't like if applications try to force focus away from my manual selection.
It is anyway only blinking in the taskbar if you try to force focus on the app with the Focus() API call.
There was a bug with Windows classic schema in 1.0.33.0 but that should be fixed with 1.0.33.1. Please make sure you use that version.

[David Kleiner]

Should be fixed after 1.0.33 patch 1