Loading old examples with converted extensions

[burkey]

Hey everyone,

I'm trying to convert the global function object to MMF 2, and it seems to be working fine, but when I load any MMF 1.5 example using the gfo, I get:

"
This application requires the following extensions:

globalfunction.mfx

Install these extensions and then click retry"

This happens even though I've placed globalfunction.mfx into the extensions directory, and I can otherwise use the extension as normal.

Has anyone else had this problem? To Clickteam: What does the MMF 2 code actually check for at this point? Just the filename and IDENTIFIER?

[Joshtek]

I've had no problems with opening old code, following the conversion instructions and giving extensions the same filename (but .mfx instead of .cox).

[burkey]

Here is one way which I can get MMF2 to run old examples:

• Move globalfunction.mfx out of the extensions/ directory
• Place globalfunction.cox into the extensions/mmf1 directory
• Load the old example
• Move globalfunction.mfx back into the extensions/ directory
• Now running the application works
• If you save to a .mfa file at this point, and then reload, you get the same error as above

Any clues?

[Anders]

I usually just take the template SDK and copy over my code to it. I don't like to use the conversion text file. IMHO this is much easier and you are sure you have the new SDK features at hand if you need them <img src="/center/images/graemlins/smile.gif" alt="" />

[burkey]

I've attached the 1.5 and 2.0 versions of the extension and a 1.5 example

[Joshtek]

I can confirm that it won't load the example.

Only thing I can think of is to check your identifier and KCX_CURRENT_VERSION.

[burkey]

Cheers Joshtek, I don't have a KCX_CURRENT_VERSION, but I do have a KPX_MARK = "MF2"

I'll give Andos' idea a try - maybe there is something particular to my extension that isn't included in the conversion routine

[Joshtek]

At the top of main.h is the identifier, and further down should be KCX_CURRENT_VERSION (just before "RUNNING OBJECT DATA STRUCTURE"). I don't know what happens if they differ.

[Anders]

I only think KCX_CURRENT_VERSION is used for Vitalize to check if there are new versions available to download. I had to increase that number for the recent AGBO update so Vitalize would download it, and I just increased it in MoveIt as well. All the old files loaded fine even when changing that number.

[Yves]

No, KCX_CURRENT_VERSION is not used at all by Vitalize, you have to increase it only each time you modify the content of the EDITDATA structure, so that the UpdateEditStructure function is called by MMF2.

If you release a new version of your extension and want Vitalize! to detect it, increase the SpecialBuild member of the VERSIONINFO in the resources.

Yves.