Add-on manager & MDID err

[Anonymous]

Hi,

I have 2 problems:

1. I'm unable to run the add-on manager application on macos (using 10.5., tried devkit 13 and 14. it just crashes before anything shows up. On windows add-on manager for devkit 12 is working, but 13&14 doesnt. the 14 version opens a database and when it closes it, it saves the database in a way it cant be opened later (says corrupted file and even a browser cant open the xml).

2. I compiled my add-on for platforms x86, x64 and macos and it worked fine, but now all the addons wont be loaded - "The file is either not an Add-On or an outdated one that cannot be used with this ArchiCAD version.". Where could be a problem? does the MDID identifier any expiration date or something like that?

Thank you, Peter

[Ralph Wessel]

santi wrote:
1. I'm unable to run the add-on manager application on macos (using 10.5., tried devkit 13 and 14. it just crashes before anything shows up. On windows add-on manager for devkit 12 is working, but 13&14 doesnt. the 14 version opens a database and when it closes it, it saves the database in a way it cant be opened later (says corrupted file and even a browser cant open the xml).

The add-on manager is a bit unstable. I've had many problems with it, but it's working at the moment on the Mac OS. I save the database into the same folder as the application though - if you save it elsewhere, the application will often crash and/or fail to write anything (so the data cannot be read back again).

santi wrote:
2. I compiled my add-on for platforms x86, x64 and macos and it worked fine, but now all the addons wont be loaded - "The file is either not an Add-On or an outdated one that cannot be used with this ArchiCAD version.". Where could be a problem? does the MDID identifier any expiration date or something like that?

The MDID doesn't expire. Are you sure the MDID resource is properly linked into the add-on? Perhaps try a full clean and rebuild, and check that the finished build has an MDID resource.

Alternatively, is it possible you inadvertently changed the MDID values? Unfortunately, the error message from the Add-on Manager is not very descriptive. It says the same thing for every error type.

[Anonymous]

I think I found the problem: I usually compile the add-on and then rename the file, where I put the add-on version and target machine like Add-On.1.0.x64.bundle and so on. I think that this is the problem for AC or the MDID, is it possible? Because than the user wont be able to rename the file...
Thanks,
Peter

[Ralph Wessel]

santi wrote:
I think I found the problem: I usually compile the add-on and then rename the file, where I put the add-on version and target machine like Add-On.1.0.x64.bundle and so on. I think that this is the problem for AC or the MDID, is it possible? Because than the user wont be able to rename the file...

Renaming an add-on shouldn't cause any problems - certainly not with the MDID. Have you confirmed that the MDID resource is present in the add-ons that fail to load?

[Anonymous]

yes, I checked that and its there. I swear that it works until I rename it. Trying to turn off and on AC, not just unplugging the add-on. Im working on AC13 with devkit 13.2517, xcode 3.2 and leopard 10.5.8.. its really weird I tried it several times

[Anonymous]

I just read a post that I should not compile addons in VS2008, it could be the problem.. even if I dont understand the behavior of addon loading that I described earlier
anyway, thanks for help