MSDN wrote:Hit testing of a layered window is based on the shape and transparency of the window. This means that the areas of the window that are color-keyed or whose alpha value is zero will let the mouse messages through.

MSDN wrote:Hit testing of a layered window is based on the shape and transparency of the window. This means that the areas of the window that are color-keyed or whose alpha value is zero will let the mouse messages through.

Well, with AutoIt it works different. I don't need to set a timer function for this kind of a GUI and that's the reason why the result is different using FB. It seems that AutoIt behaves different than what MS suggests. In AutoIt you don't need necessary to work with WMs. If you are interested to see the AutoIt code then have a look here: _WinAPI_MarkScreenRegionAndCaptureThe trick with the SetTimer worked - thx.

I tested this code in my office with 3 monitors and the cross-hairs follows the mouse properly. The DPI is set to normal. Further, I just started with it... ;-)

I also tested it in the office :-) but with a laptop (150% scaling) connected to a monitor (100% / no scaling). Depending on whether the application (console) was positioned on the one display or the other it worked or didn't. As you do not face issues i assume it's related to HiDpi. Maybe the app just needs to be marked as dpiaware - I haven't tried.

St_W wrote:I also tested it in the office :-) but with a laptop (150% scaling) connected to a monitor (100% / no scaling). Depending on whether the application (console) was positioned on the one display or the other it worked or didn't. As you do not face issues i assume it's related to HiDpi. Maybe the app just needs to be marked as dpiaware - I haven't tried.

Can you try this when you are in your office again if it displayed properly please?

UEZ wrote:Can you try this when you are in your office again if it displayed properly please?

No, unfortunately doesn't fix the issue. However, I tried setting HiDPI override to "application" in the compatibility settings and this does work. So dpi-awareness seems to be the issue, but your fix doesn't work somehow. Probably it needs per-monitor dpi awareness, because my monitors use different scaling settings?I've implemented a tiny dpiAware demo a while ago and tried using the application manifest from that demo with your application and that worked.http://users.freebasic-portal.de/stw/fi ... e-demo.zip

UEZ wrote:Can you try this when you are in your office again if it displayed properly please?

No, unfortunately doesn't fix the issue. However, I tried setting HiDPI override to "application" in the compatibility settings and this does work. So dpi-awareness seems to be the issue, but your fix doesn't work somehow. Probably it needs per-monitor dpi awareness, because my monitors use different scaling settings?I've implemented a tiny dpiAware demo a while ago and tried using the application manifest from that demo with your application and that worked.http://users.freebasic-portal.de/stw/fi ... e-demo.zip

Hmm, as I don't have that issue what is your issue? I assume the mouse cursor is not at proper position (middle of the cross-hairs).I changed 2 of 3 of my monitors to different scale value and tried "PROCESS_PER_MONITOR_DPI_AWARE" as value and it seemed to work properly if this was the case.Thanks for the manifest. I will test it later...