Gangula

Hi @Tihiy, Maybe this flew under the radar, so I'd like to check again. Is SAB controlling the display of the list of open windows for an application icon in the taskbar? It seems that the width of the list is now dramatically smaller when there is a big number of windows for a single application. Before the list was wide enough to accommodate the longest window caption (or something like that). Thanks in advance!

Thanks for the advice. I have seen that with SAB versions prior to v3.8, when you click on the Start button, there are 2 events generated. One from the [Desktop]->[Button with caption "Start"], the other from [Shell_TrayWnd]->[Start with caption "Start]. With version v3.8+ there is no second event happening anymore. Is this intentional? Thanks!

@Tihiy Thank you very much for the prompt reply. Sorry, I made a mistake. I copied the code responsible for intercepting Windows Key. I can confirm that when I press the Windows Key with the SAB v3.8, I get my dashboard instead of the standard Windows Start menu (as it was in v3.7). I figured out what is the difference between v3.7 and v3.8 that's affecting me. The Start button prior to v3.8 has a window caption "Start". After the SAB rework the caption is empty.

Hi everyone. Just upgraded from 3.7.7 to 3.8.4. I guess that the big rework done in v3.8 changed something relevant to my use case. I'm a "weekend programmer" at best and I have created long time ago a "replacement" for start menu for myself (kind of a dashboard that suits my needs and ways of working). Essentially, I've been intercepting the "clicks" on the Start button and displaying a form I created instead of the Windows Start menu. With Windows 11 that stopped working because of the modification they did on the whole taskbar area. While looking at different tools to customize Windows 11 Start menu and taskbar, I realized StartAllBack actually made it possible for me to continue using this application again. It seems it was exposing "the right" "handle" again that Windows 11 "reworked" and removed (which was available in Windows 10 and Windows 7). With version 3.8 my app stopped working. Probably the rework that was necessary on SAB affected also the existence/availability of the mentioned "handle". This is probably question for @Tihiy. Would it be possible for SAB to bring back the possibility to intercept Start menu calls via the following messages? if (code == HC_ACTION && wParam) { MSG* msg = (MSG*)lParam; if (msg->message == WM_SYSCOMMAND && (msg->wParam & 0xFFF0) == SC_TASKLIST) { HookMsg info; info.lParam = lParam; info.wParam = wParam; info.nCode = code; ... I see a mention in the previous post (by kitcat) that Start Menu X stopped working with SAB. I believe it would be for the same reason as it probably hooks into the same handle. Thank you very much in advance!