Replies: 1 comment
-
|
if they are Windows system commands (not registry added) - yes, it is possible, but it is not so simple to be practical. Windows commands can be called with ID. Windows can use the same name and have different commands (with different IDs) attached to this name: refresh in explorer and refresh on the desktop are not the same - at least I am sure of that. Even if you find all the IDs for a given command with the next update Microsoft can change the ID, the old one will work if it is not removed, but they often delete it with the next update - the commands in the taskbar are a real example |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I’m not very familiar with how Nilesoft Shell works internally, but I have an idea/question.
For example, take the native Windows context menu item
Copy as path:Copy as pathitem;ItemBusingitem()in Nilesoft Shell;ItemBis clicked, directly invoke the original WindowsCopy as pathaction itself(not reimplementing the behavior, and not using
commandsto simulate it).One reason I’m interested in this is that the order of native context menu items is often uncontrollable. Also, some third-party menu items are implemented through DLL-based shell extensions and parameter passing, which makes them difficult or impossible to reproduce using
commands.So I’m wondering whether it’s possible to hide the original native item and create a Nilesoft Shell “proxy” item for it instead. From Explorer’s perspective, it would still behave as if the original native menu item had been clicked directly.
Beta Was this translation helpful? Give feedback.
All reactions