How do you "run" a plug-in?

Discuss and announce Total Commander plugins, addons and other useful tools here, both their usage and their development.

Moderators: Stefan2, white, sheep, Hacker

Post Reply
User avatar
MarkFilipak
Member
Member
Posts: 106
Joined: 2008-09-28, 01:00 UTC
Location: Mansfield, Ohio

How do you "run" a plug-in?

Post by *MarkFilipak » 2018-04-20, 00:17 UTC

I installed the NTLinks WDX. How do I "run" it?

There are Win10 links:
  • c:\Users\All Users\Application Data\Start Menu\
    c:\Users\All Users\Start Menu\
    c:\Users\Default\Start Menu\
    c:\Users\Default User\Start Menu\
    c:\Users\mark\Start Menu\
and in all of their property sheets, the 'Target' attribute is empty. I need to identify the targets. Win10 is messing with my Start Menu items.

Do WDXs have user interfaces? Where are they?

Thanks.
Hi Christian! Delighted customer since 1999. License #37627

User avatar
Dalai
Power Member
Power Member
Posts: 6693
Joined: 2005-01-28, 22:17 UTC
Location: Meiningen (Südthüringen)

Post by *Dalai » 2018-04-20, 02:30 UTC

http://www.ghisler.ch/wiki/index.php?title=Content_plugin should tell you everything you need to know about WDX plugins.

Regards
Dalai
#101164 Personal licence
Athlon X4 880K, 16 GiB RAM, Gigabyte F2A88X-D3HP, Win7 x64

Plugins: Services2, Startups

User avatar
MarkFilipak
Member
Member
Posts: 106
Joined: 2008-09-28, 01:00 UTC
Location: Mansfield, Ohio

How do you "run" a plug-in?

Post by *MarkFilipak » 2018-04-20, 03:29 UTC

Dalai wrote:http://www.ghisler.ch/wiki/index.php?title=Content_plugin should tell you everything you need to know about WDX plugins.
Thanks for replying, Dalai, but there's no "Use" information (or link) in the wiki page about the NTLinks WDX, and the plug-in's author doesn't document how it's used (or launched). I was hoping someone here would know.

It did install, and I do need it to defend against the stunts that Win10 does in its misbegotten attempt to control its users (Me!). You see, I had 2 programs in my Startup directory, but Windows decided to delete them, but then, they still run on Startup (and they're not on a "Run" line in the Windows Registry). ...Windows 10 is driving me to suicide.
Hi Christian! Delighted customer since 1999. License #37627

User avatar
MVV
Power Member
Power Member
Posts: 8322
Joined: 2008-08-03, 12:51 UTC
Location: Russian Federation

Post by *MVV » 2018-04-20, 05:52 UTC

Usually WDX plugins are used to retrieve some information in tooltips or custom columns (I mostly use it in tooltips where I see the target and real path because I don't use custom columns often). In attributes dialog WDX plugins are mainly used for setting values, so initially fields are empty, thats by TC design. However you can click ">>" button near the field and plugin will put current link target path into the field.

User avatar
nsp
Power Member
Power Member
Posts: 1213
Joined: 2005-12-04, 08:39 UTC
Location: Lyon (FRANCE)
Contact:

Post by *nsp » 2018-04-20, 06:43 UTC

MVV wrote:Usually WDX plugins are used to retrieve some information in tooltips or custom columns (I mostly use it in tooltips where I see the target and real path because I don't use custom columns often). In attributes dialog WDX plugins are mainly used for setting values, so initially fields are empty, thats by TC design. However you can click ">>" button near the field and plugin will put current link target path into the field.
All WDX works the same !
Some plugin have embeded ui you can reach with rundll to run it directly generally to configure it. The safiest way is to give a look to open source project that use it like : AHK Multi rename script or Super WDX or WDX guide or even double commander....

User avatar
MarkFilipak
Member
Member
Posts: 106
Joined: 2008-09-28, 01:00 UTC
Location: Mansfield, Ohio

Post by *MarkFilipak » 2018-04-20, 07:24 UTC

MVV wrote:Usually WDX plugins are used to retrieve some information in tooltips ...
Wouldn't the context menu be more convenient? Or Properties? -- though you probably don't have access to property sheets.
... In attributes dialog WDX plugins are mainly used for setting values, so initially fields are empty, thats by TC design. However you can click ">>" button near the field and plugin will put current link target path into the field.
With your clues, I stumbled into it. ...I would never have guessed...

NTLinks is your plug-in, isn't it?

What about this as a general WDX solution: If TC had an "Extended Properties" drop target to which plug-ins could add functionality, then users could drag a file/directory to the drop target to get/display extended properties (including target for <LNK> objects). All of that functionality could be internal to TC and, therefore, not reliant on context menus or attributes. And, WDXs would not need to be configured.

PS: I should explain a little more. ... All you (WDX authors) need is the path/name of the file or directory, right? Well, what if there was a text line for users to enter path/name... but of course, even better, let the user drag a file or directory to the drop target and let the drop target pass the path/name string to your WDX. Get it?
Hi Christian! Delighted customer since 1999. License #37627

User avatar
MVV
Power Member
Power Member
Posts: 8322
Joined: 2008-08-03, 12:51 UTC
Location: Russian Federation

Post by *MVV » 2018-04-20, 07:38 UTC

Wouldn't the context menu be more convenient? Or Properties? -- though you probably don't have access to property sheets.
As nsp said, all WDX plugins work in the same way, they use the same interface which allows to use them for retrieving values (in tooltips, custom columns, multi-rename tool etc) or setting values (in attributes dialog). WDX plugins don't have any access to context menus.

If you wanna a more convenient way of creating links, you can try my NTLinks Maker tool which only creates links with TC-style dialog.
Last edited by MVV on 2018-04-20, 08:09 UTC, edited 1 time in total.

User avatar
MarkFilipak
Member
Member
Posts: 106
Joined: 2008-09-28, 01:00 UTC
Location: Mansfield, Ohio

Post by *MarkFilipak » 2018-04-20, 07:57 UTC

MVV wrote:... WDX plugins don't have any access to context menus ...
Well, I guessed that would be the case. That's why I suggest a WDX extended properties drop target in the 2nd half of my post. What do you think of it?

PS: I'm not creating links. I'm trying to discover the target of Windows links when Windows hides the target string.
Hi Christian! Delighted customer since 1999. License #37627

User avatar
MVV
Power Member
Power Member
Posts: 8322
Joined: 2008-08-03, 12:51 UTC
Location: Russian Federation

Post by *MVV » 2018-04-20, 08:12 UTC

PS: I'm not creating links. I'm trying to discover the target of Windows links when Windows hides the target string.
I don't think that context menu is a good way of viewing file property. I've said how I do it: I use tooltips. Open Configuration, Display, Help texts, User-defined, add file/folder mask or template, OK, type custom field expression, e.g.:

Code: Select all

Real path: [=ntlinks.Real path]\n[=ntlinks.Object Type]: [=ntlinks.Target path]\n
(I use this expression for reparse points only, i.e. in file template I have rule "tc.file type = reparse point")

Post Reply