How can I extend the context menu of a wfx plugin

[pi]

Hi folks,

I just wrote a little FS plugin for a serial storage device.
Now I need to extend the entries of the device context menu.
The menu currently looks like that:

• [\My_Device]
  Eigenschaften

("Eigenschaften" is "properties" in German).
The latter one I use to set the serial communication parameters like Com port and baud rate.
But I need two special functions for the device, so I want to extend the context menu to offer these functions.
The sample plugin and the wfx plugins with source code available (Ext2+/Reiser, HTTP browser, WinCE) don't provide such an extension and the FS-Plugin writer's guide doesn't address that theme.

So maybe you can give me a clue?

Language is VisualC++ (in fact, my code is native C).

Thanks in advance,
pi

[tbeu]

I believe context menu extension is just not possible. But there are quite some alternatives here as you may probabely have seen from other file system plugins.
1) Display "dummy" files or directories which show your required information when they are opend or entered, respectively.
2) Add strings to the command line which get caught by the third parameter of FsExecuteFile.

TBeu

[Lefteous]

http://www.ghisler.ch/wiki/index.php/Custom_context_menus_in_file_system_plugins

[pi]

@tbeu: since my device contains a real (FAT) file system, 1) is not appropriate.
2) may be an idea, but how shall I invoke the extra commands?

To be a bit more specific, the extra commands are "create image from device" and "put image on device". These are functions that don't operate on files but on the whole device.

@lefteous: THAT'S IT! But it seems to be a wish list rather than an existing way to do it... 8-(

[majkinetor !]

It can be done via hooks (not system hooks, since your code will run inside TC)

You have to monitor popup class.
Alternative is to set custom button text in F3 F4... F8 function buttons and to catch that event. TO do so you can sublass button class to catch events , get the handles before that, change the name of the buttons (for instance you can set on F4 Properties) etc...

Ohter solution is to monitor right mouse clicks, also via local hook, and to forbid TC to show its own menu while your plug is active, then you can display your popup .


ALl solutions are quite easy, so it all depends on how you handle Windows API programming.

[pi]

You have to monitor popup class.

Never done that...

Alternative is to set custom button text in F3 F4... F8 function buttons and to catch that event. TO do so you can sublass button class to catch events , get the handles before that, change the name of the buttons (for instance you can set on F4 Properties) etc...

This is a bad idea since one of the main advantages of TC is that you can use it blindfolded - so re-using these function buttons leads to chaos and anarchy!

Ohter solution is to monitor right mouse clicks, also via local hook, and to forbid TC to show its own menu while your plug is active, then you can display your popup .

Also a solution that disables some of TCs features. I would prefer a solution that does not interfer with existing functions.

ALl solutions are quite easy, so it all depends on how you handle Windows API programming.

Well, in my plugin I don't handle Windows API programming at all (at least now). The only "GUI" I use is done via RequestProc() to get the com port parameters.

[majkinetor !]

2pi
Oh pi, you are not searious programmer nor your arguments are good. I don't have time to explain now, hopefully you will understand one day.

Sorry to take your time.

[tbeu]

2pi
Because you already know how you want the popup to look alike you can recreate the popup by use of local hooks as majkam said.
My_Device
Properties
Create image from device
Put image on device

[pi]

@tbeu: OK, as I said: Never done that. Can you give me an example?

@majkinetor: You are nearly right: I am not a serious Windows GUI programmer.

[tbeu]

2pi
You need to be a serious programmer if you want to be a serial programmer
To be serious I have not yet programmed hooks. The one application I know that uses hooks is CLCL. Maybe you can learn from it. But not sure if system or local hooks.

[pi]

@tbeu: Thanks, I will have a look at it. Well, in fact I am a serial programmer!

And I am still willing to learn things I can't do now. Maybe majkinetor will have some time for me in the future...

[XPEHOPE3KA]

You need to be a serious programmer

Well, pi isn't saying anything against it =) :

I am not a serious **Windows GUI** programmer.

[majkinetor !]

Maybe majkinetor will have some time for me in the future...

Yes he will

The local hook is sufficient for you.
CLCL is wrong choice to do learning. It is on Japanise, and is very complicated.

You have many examples on the net how to hook, it is well known technique. Basicly you call some function that installs hoook, you give her pointer to your function that will Windows call on events you want to monitor, set the hook type, and thats it. You can later choose to process event, to skip it, or even to forbid hooked application to receive it. System hooks are far far wors, but they are needed to handle windows in other adress spaces and you don't need that since you are controling TC within TC. So, you got the easier part.

[djorge]

I have no experience with Hooks, but won't the other FSPlugins show the new items too in context menu?

[ghisler(Author)]

I recommend that you do NOT use hooks and other dirty tricks to put your menu items into Total Commander. Why? While this may work perfectly with the current version of TC, it's possible that it will not work with future versions (e.g. because there may be actually a context menu interface), or with other programs which use the plugin...