Re: FxPlug versioning
Re: FxPlug versioning
- Subject: Re: FxPlug versioning
- From: Martin Baker <email@hidden>
- Date: Thu, 28 Mar 2013 17:12:46 +0000
| Hi Christoph
Not sure I understand. The BOOL has a default value of NO, and is only set to YES if the popup migration has taken place. For a previous instance of the plug-in, the BOOL doesn't exist, so it should have the default value of NO.
It's a bit immaterial anyway though if the versionAtCreation is never returning v1 with the v2 plugin in a v2 template!
Martin ------------------------------------------------------ Digital Heaven Ltd is registered in England and Wales Company registration number: 3628396
Registered address: 55 Lynwood Drive, Worcester Park, Surrey KT4 7AE
VAT registration number: GB 736 0989 03
On 28 Mar 2013, at 15:11, Christoph Vonrhein wrote: The problem is that the new version of the plugin adds the Bool parameter to the V1 project and so you will always wind up with V2. It might have worked if you've added a hidden INT to the project declaring the version of the plugin used in the project. Then the parameter will not be overwritten be the new version of the plugin.
|
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden