export of CommandIds to access internal menus from scripts

Features wanted...
Post Reply
roemer_m
Posts: 12
Joined: 10 Dec 2016 15:18

export of CommandIds to access internal menus from scripts

Post by roemer_m »

I'm trying to extend the context menu via custom event actions (CEA) in file list. I'm using popupnested command to activate the menu and it would be very nice to include as topics internal xyPlorer menus like the default folder context menu (used if I configure CEA to Pop up folder's context menu => see snapshot) and maybe some (Pop up tabs, ...) more that currently not exported by command-Ids.

An additional idea might be to extend xyCommand 'cea(index, [action], [script])' to call the other configurable internal actions from CEA-action scripts itself.
Proposal is to use a special identifier "Call" or "Invoke" to invoke the standard procedure calls (detection mechanism might be useful to prevent endless loops). It opens possibilities to intercept events via CEA only to catch or set information for further activities (changed paths, called files etc.) without the need to handle events completly by own script.

"CEA_TreeRightClickOnWhite"
prNotifyCustomEventAction("CEA_TreeRightClickOnWhite"); // notify + log
writefile("P:\HistoryXyplorer.txt", tab("get", "path") . <crlf>, "a", "tu"); // store current path in history file
cea(6, 2, "Invoke"); // call default pop up folder context menu
Attachments
Command Id of context menu.PNG
Command Id of context menu.PNG (34.02 KiB) Viewed 5005 times

Post Reply