Explanation of structure s_TCommand

[Ron]

If you want to 'bind' your plugin to a command set the

actiontype to your plugin number and call SetCommand(..)

[Ron]

The first couple of fields are not of interest to a plugin, they are there for completeness sake.

The fields that are of interest to you are:


BYTE actiontype;
BYTE actionsubtype;
PCHAR svalue1;
PCHAR svalue2;
_BOOL bvalue1;
_BOOL bvalue2;
_BOOL bvalue3;
int ivalue1;
int ivalue2;
int lvalue1;
int lvalue2;
int lvalue3;


Actiontype Your plugin number
ActionSubType IF your plugin has more then one action specify which of those actions here.
sValue Store a string here ( Use realloc pchar )
iValue Store an integer here.
bValue Store booleans here.
lvalue Store link-ids here ( get them through the treepicker.

[lospalos]

Hallo,
I had problem to bind my pluggin to commands defined at tree. the problem was i didn't understand meaning of fields in structure s_TCommand. Can somebody explain me meaning of each field in command?
LosPalos

[lospalos]

thanks Ron,
i did it already, pluggin works now fine,
but i would like to go deeper therefore i need to understand all fields, not only ActionType.