XeNTaX

SUCCES!

It worked! I could now retrieve the filenames !

I sent you the recompiled test app.

Question is, do I need more than the filename? I also get an Internal FindInfo, which is a uint32 (long, DWORD etc). Is that correct?

Yes, thats a pointer to memory that the program controls

the InternalFindVar is a variable that COM plugins will use, since VB can't use pointers, i provided a Variant, for it to use instead of the Info, the raw programs like C/C++/Delphi can use the pointer to speed it up.

Umm no, well you can

There are 2 ways to extract, by name(wildcard) and by index, you should also be able to say mpExtractFileByIndexToXXXXX, or mpExtractFileByNameToXXXXX

depending on the plugin, you can query using the mpFileFirstFile/mpFileNextFile for other info as well.

Right now BFFileFormat doesn't have any options, but i could add some if you want

the way it works is

FindFileInfo.FieldList = "FileSize;FileAttrib;"

and after the First/Next you get FindFileInfo.FieldData = "1234567;500" where the first number is the file size and the second number is the value of the attributes of the file

you could make some fields manditory, and you can query the plugin for valid fields.

Note: there could be 2 different file sizes as well, a compressed filesize and a real file size

I will have to check, 'cause I believe my FieldData was "" (empty).

Whether Mr. Mouse MultiEx Commander supports plug-ins there is an example of their writing? (it is desirable on Pascal - Delphi) it is possible and on Basic

It is possible on basic, although, THAT support is more experimental than what we are working with. At least until someone works with me to get that side working.

Right now, VB is supported via COM DLL similar to the old DLL, but with functions that are the same in RAW DLL.

Strange as that... In folder Plugins 3 plug-ins lay and MultiEx Commander sees only 2...

I have noticed that as well. Weird. Especially, since it does show in the list if you wish to open an archive.

It's a bug, and on my to-do list for the next release.

Perfectly... We Shall wait next release.

Kornet, the new plugin system is actually written in Delphi.

OK, as I saw, the FieldData in TFindFIleInfo is en empty string after mpFindFirst/Next . Is this correct? Do I have to tell the manager to give me the details (like offset size etc)?

You have to ask for it, yes, in the FindFirst, but you also have to know which fields the plugin supports.

Rahly wrote:Kornet, the new plugin system is actually written in Delphi.

It pluginmanager.dll?

the new plugin system isn't implemented in mexcom at the moment, its being worked on by Mr Mouse

I found out something Mr Mouse, I need to try something to see if it works. I need to send you a new copy of the manager to test though.

Ok, send it!