[Feature Request/Bug] Support for appgroup shortcuts on the desktop

[UndeadKitten]

Currently when you click on the appgroup shortcut on the desktop, the popup only appears near the bottom taskbar.

I'd like to use the appgroup shortcut on the desktop instead of the taskbar.

Desktop shortcut issue example:

I'm a bit of a layman but from my testing it appears that the popup window already positions itself based on the horizontal position of your mouse, or the vertical position of your mouse if you have your taskbar vertical on the side of your screen. It also appears to distance itself from the edges of the screen and the edges of taskbars.

Since both of those functionalities already exist, would it be possible to position the popup window based on both horizontal and vertical position of the mouse, without introducing a new issue of overlapping the edges of the screen and taskbars?

Adding support for this (making the popup window appear at mouse position) may also function as a workaround fix for a compatibility issue with another github program called Linkbar that adds additional taskbars.

I'm tested this on Windows 11 Version 25H2 (OS Build 26200.7462), and with AppGroup v1.3.0.

[UndeadKitten]

Here are some additional screenshots of tests, if you're interested:

I used two different programs to test different taskbar positions, one is StartAllBack, and the other is Linkbar.
When I write "taskbar", I used StartAllBack to reposition the taskbar in that test. When I write "linkbar", I used Linkbar to create an additional taskbar in that test.

Clicking the desktop shortcut positioned at the edge of the screen:
In addition to the main issue, maybe a minor issue with spacing consistency, the popup is 15 pixels from the taskbar, but only 7 pixels from the edge of the screen.

Clicking the shortcut on a top taskbar (autohide ON & OFF):
Works correctly, the popup appears at the top of the screen instead of the bottom, minor inconsistency with the spacing however, 8 pixels away from the top taskbar instead of the expected 15 pixels. Functionality remains the same regardless of autohide setting.

Clicking the shortcut on a top linkbar (autohide OFF):
Functions the same as the test above.

Clicking the shortcut on a top linkbar (autohide ON):
Same issue as the desktop shortcuts, the popup appears at the bottom of the screen.

Clicking the shortcut on a side taskbar (autohide OFF):
Works correctly, the popup appears at the correct height, next to the shortcut. The popup's distance from the side taskbar is consistent with the bottom taskbar, both being 15 pixels.

Clicking the shortcut on a side taskbar (autohide ON):
Works mostly correctly like the previous test, but the popup no longer respects the side taskbar's boundaries when autohide is ON.

Clicking the shortcut on a side linkbar (autohide OFF):
The popup doesn't appear near the shortcut or mouse. The popup does respect the side linkbars space, not overlapping with it, which is nice. But the spacing inconsistency is more noticeable in this scenario with a side linkbar present, 7 pixels from the side linkbar, while 15 pixels from the bottom taskbar.

Clicking the shortcut on a side linkbar (autohide ON):
The popup doesn't appear near the shortcut or mouse, like the above test. But it no longer respects the boundaries of the linkbar with autohide ON, which I'd consider expected behavior and fine.

Clicking the desktop shortcut positioned at the edge of the screen with a side linkbar present (autohide OFF):
Still has the main issue and the minor spacing inconsistency mentioned in the first test, but it's respecting the side linkbar's boundaries again which is nice.

I also tried changing the size of the taskbars through both programs to see if it would effect the margins/distance of appgroups popup window, and neither had any effect on the edge-to-edge distance between the appgroup popup and the taskbars. (Eg. distance from the top linkbar remained at 8 pixels regardless of the linkbar's size.)

My screen resolution is 1920x1080.

[iandiv]

this feature is part of the upcoming release. It’s already implemented and currently going through testing, optimization, and bug fixes.