desktop files for that, it is even an open standard anyone can implement (even Microsoft, let's hope they will do eventually) Of course, other applications may need more complicate interaction, but why adding such complications to pass what is basically, for what regards most applications, a simple sequence of strings? On any MS and non-MS operating system since the '90s. bat file, will fully accomplish the task. even dragging files over the executable, or a. SendTo is based on plain, simple links and yet is more than sufficient to do all of that. Returning to context menu entries, I basically need only a method to pass single or multiple input file names to the application. Old and new COM based methods (please mind IExplorerCommand was published altogether with SubCommands in Windows 7, when this documentation was written) were (rightfully) seen as adding unneeded complication for a such simple task, and should have become the exception not the rule.Ībout sparse manifests, there is some documentation about using various tools to accomplish this signing and registering Win32 applications at runtime which seems quite convoluted and more related to force msix concepts to developers rather than with context menu performances itself. More code, more possible bugs, more things that can go wrong that can be replaced by a simple SubCommands registry entry for most common cases. In Windows 7 and later, you should resort to COM code-based solutions only when the static methods are insufficient." Prior to Windows 7, the creation of cascading menus was possible only through the implementation of the IContextMenu interface. "In Windows 7 and later, cascading menu implementation is supported through registry settings. What really shocks me is that the MS decision completely contradict what is reported by the very MS documentation about static verbs SubCommands as THE solution, introduced in Windows 7, to reduce the burden of running multiple COM objects to do what a simple registry key could accomplish So far no luck in finding working examples for Lazarus/FPC or Delphi (closest commercial language) for implementing a COM object to use IExplorerCommand method.īut this is a limitation of my programming skills and time to devote to the project, nothing to blame someone else about - even if, being this an open source project, I can hope in code contributions in this sense. Premise: I'm talking of an unfinished product, so this answer is far than conclusive.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |