Is this autohotkey limitation or there is something wrong with everything...or maybe that's just how the menus work
Unless I activate the View menu at least once after I start Everything,I cannot use AutoHotKey command like WinMenuSelectItem
Call the sidebars with messages?
Re: Call the sidebars with messages?
First guess:
Everything draws its own menus without using the Windows menu API's (at least in dark mode; not sure about "light" mode).
WinMenuSelectItem will likely expect "normal" menus.
Maybe one of the Command IDs can help here ...
Everything draws its own menus without using the Windows menu API's (at least in dark mode; not sure about "light" mode).
WinMenuSelectItem will likely expect "normal" menus.
Maybe one of the Command IDs can help here ...
Re: Call the sidebars with messages?
This did the job,thanks
SendMessage, 0x111, 40192,,,Everything ; tree
and
SendMessage, 0x111, 40055,,,Everything ; preview
SendMessage, 0x111, 40192,,,Everything ; tree
and
SendMessage, 0x111, 40055,,,Everything ; preview
Re: Call the sidebars with messages?
The menus in Everything are non-standard.
Menus in Everything are not the typical menu resource.
Menus in Everything are dynamically generated when shown.
They do not exist until you open the menu.
The dark mode uses the standard "menu".
Everything only handles the rendering of the menu bar.
I will look into generating the menu on startup so WinMenuSelectItem will function correctly.
For now, it's best to send the Command ID directly (as NotNull mentions)
Menus in Everything are not the typical menu resource.
Menus in Everything are dynamically generated when shown.
They do not exist until you open the menu.
The dark mode uses the standard "menu".
Everything only handles the rendering of the menu bar.
I will look into generating the menu on startup so WinMenuSelectItem will function correctly.
For now, it's best to send the Command ID directly (as NotNull mentions)