Quirky Help Window Behaviour (2.2.6.1)

[Grumbler]

Hi,

Recently downloaded Wings 3D v. 2.2.6.1 and noticed that the windows that open in the Help menu have the following strange behaviour.

Startup Wings3d
Mouse over the Help menu
Select e.g. Getting Started - window appears
Move mouse away from menu/window - window disappears, still showing in Win10(x64) Taskbar
Activate by mouse Getting Started from Win10 Taskbar - window reappears, then disappears. Still active in Taskbar.

This behaviour happens with other Help menu selections. I'm not a programmer, but it looks like Wings3D is reclaiming focus back to the main window maybe.

Wings 3D v. 2.2.6.1
Win10 Home (x64)

HTH

Edit to add: Does not happen in v2.2.3 or v2.2.5

[micheus]

Quote:I'm not a programmer, but it looks like Wings3D is reclaiming focus back to the main window maybe.

Yes. That is what is happening.

I guess they work this way intentionally.
These windows are intended for eventual information and also they cannot be docked - In opposed of the windows you find under Windows option which they stay over the main window and we can dock them since they are of more intense use.

[Grumbler]

Thanks for replying, I think I understand.

If the help windows could stay on screen for just a little while longer before minimising to the Taskbar it would be helpful, as once they have minimised then they minimise immediately when trying to read their content.

The only way to stop this from happening is to open a Help window and not allow the mouse pointer to leave the window, this prevents the main app from stealing focus.

Have also noticed, that the help windows once opened and allowed to close by Winds3D main app, then they stay available on the Win10 Taskbar until closed manually by right-clicking the Taskbar and closing it that way.

Hope this explains things more clearly - it is far easier to observe than explain.

Grumbler - Love Wings3D despite my name

[micheus]

Ok. I'm going to take a look on this.

[Grumbler]

Thank you

[micheus]

I checked and the problem was introduced in v2.2.5.

I'm presenting a suggestion to correct that which still needs to be approved by the main devs. If accept, it should be available in the next release.

Thanks for report.

[Grumbler]

Thank you Micheus for looking into this.