Imageglass: Stays on top even when it shouldn't

[SeriousHoax]

System information:

• Windows OS version: Windows 10 Pro 1903
• ImageGlass version: 7.0.7.26

To Reproduce

Steps to reproduce the behavior:

1. Open three or more images in a row with multiple instance turned off and often Image Glass would stay on top even when Always on top is turned off.

Actual behavior:

Stays on top even when it shouldn't.
Check the attached GIF file.

Expected behavior:

Should not stay on top

Screenshots:

[d2phap]

Hi @SeriousHoax
How often does it happen? I am unable to reproduce it though.

[SeriousHoax]

Hi @SeriousHoax
How often does it happen? I am unable to reproduce it though.

It's happening every time for me. The way I showed in the GIF. After opening first two images, Image Glass was on foreground like the way it should be but when I opened the third image, Image Glass wasn't on foreground anymore. Check the color of the title bar. Black means it's on foreground and white means it's not. Then when I click on areas outside it doesn't go away until I click back on Image Glass to make it a foreground app again.

[fire-eggs]

I'm seeing it. This is a subtle one: why does IG behave correctly for the second image, but fails for the third?

From an internals perspective, this would be described as "IG is the foreground window, but does _not_ have focus". After double-clicking on the third image, IG should be both the foreground window and have focus.

[SeriousHoax]

Any update on this issue?

[fire-eggs]

Thanks for the reminder. A fix should ship with the upcoming release.

[SeriousHoax]

The new version kind of fixed the problem but it created another similar one. This happens when "Allow multiple instance of the program" is turned off. Anything after second image doesn't come to foreground maybe or something like that. Also it takes longer than before to open an image. The process has become slower with this release. Try to improve that as well. Anyway, Check this:
https://imgur.com/a/K8RHur8

[fire-eggs]

Oooh, thanks for the video! I'll have to take another look.