loadMetaData nullPointerException

Something funny’s happening with the new patches. After the importer has done it’s job, the ModuleManagerWindow goes through it’s list of modules again and finds an ADC2 OPS file that is not a valid archive (obviously). It then calls setValid(false) which terminates VASSAL with an exception.

Where does the OPS file get called an archive and how do I fix it?

Thus spake “mkiefte”:

I know what the problem is. I’ll fix it right now.


J.


Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)

Thus spake Joel Uckelman:

There you go. It’s fixed in trunk@3649. The problem was that loading
anything told the ModuleManager “NOTIFY_OPEN_OK”, which tries to add
the module to the list. But there’s no module file yet when you import.
I changed it so that “NOTIFY_IMPORT_OK” is returned and no attempt
is made to add the module to the list at import-time.


J.


Messages mailing list
Messages@forums.vassalengine.org
forums.vassalengine.org/mailman/ … engine.org

Post generated using Mail2Forum (mail2forum.com)