[Anchors] Improve the auto position system to support all cases

[gileli121]

Sometimes the auto-position system will fail to move the anchors away from texts or images.
Examples of such cases (reported by @cpasoft):

The reason is that the existing UI Automation API failed to detect the elements on the window below the anchors.
When the OS does not know what the window shows, it can't report to WindowTop where the texts are.
As a result, the system in WindowTop will not able to calculate available positions because it has no information about where the texts/images are located.

Until now, it was impossible to fix this issue.
But thanks to what found here: microsoft/Windows.UI.Composition-Win32-Samples#97 (comment)

It should be possible to screenshot the window silently and then use fallback logic that will try to map the location of empty spaces" (where there is no text/image) using image processing.
After the mapping is done, the system will know where to move the anchors

[cpasoft]

I've tested the "auto position system" on others app, and not working either...
Typora is another example of this wrong behaviour.
Improve this system would be great, but I don't know how will it affect in processing time.
I've disabled the "auto position system" and set the right side position for the anchors. I think this is enough for me by now.
Anyway, I'll do any test you need if you finally decide to improve this system...

And as always, thank you for your efforts and dedication...

My best regards...

[gileli121]

but I don't know how will it affect in processing time

I also don't know. I have some tricks.
You probably think that because it will be based image processing it will work slower but you may be wrong.
I know how to write very efficient algorithm for this job.
In addition, I will add roles for when and how to reduce the processing

I've disabled the "auto position system" and set the right side position for the anchors

This is what I don't like. If you disabled it, it mean that it is not good enough so need to be fixed

[cpasoft]

This is what I don't like. If you disabled it, it mean that it is not good enough so need to be fixed

Then, let's go for it... i will help you in any way i can!!! 👍
:-)

[gileli121]

After about 3 days I finally start to get it right

But it is still not working perfect. There is more work to do here.
At least there is good POC

[cpasoft]

Great news... It sound promising... Keep doing!!!
👍

[gileli121]

This is extremely complex.
I will have to rewrite it 2-3 times until it is finalized.
But this is why I so like it.. It is better than playing games

[gileli121]

@cpasoft
Finally I got it right now

Do you use Windows 10 or 11?
It may not work in Windows 10 because the new API missing some feature in Windows 10

[cpasoft]

Uooohhh... It's look impressive!

I've use both OS, but mainly Windows 10.

[gileli121]

We will have today or tomorrow first beta version.
Just need now to move all the code to interface so that I can create one implementation for Windows 10 and one for Windows 11.
It will use the new implementation in Windows 11. In Windows 10 it will use the old implementation so you will not see the improvement in Windows 10. This is until the new API will be fully available in Windows 10 also.

I also found that the new implementation using 10% GPU.
Probably this can be fixed by reducing the capture frame rate...
The auto-position algorithm do it's job every 1 second.
But there are multiple threads that in each thread it capturing non-covered window.. These threads capturing each window in very high frame rate so I think that reducing the capture rate will fix it

[gileli121]

I fixed the 10% GPU usage. Now it will use up to 1.5% according to my tests.
Indeed - reducing the capture frame rate solve it.

[cpasoft]

Great news... Waiting for test it... 😃