Dnia środa, 12 czerwca 2013 o 12:27:10 Sandro Santilli napisał(a): > On Sun, Jun 09, 2013 at 10:27:51AM +0200, Borys Jurgiel wrote: > > Actually no breaking change happened now, there would be just MUCH more > > switches (assuming that e.g. each formerly QString-type variable may be > > either QString or unicode). So in the simplest plugins you can still use > > them and make the plugin dual-API-compatible. Just remember to > > explicitly set both qgisMinimumVersion and qgisMaximumVersion, otherwise > > QGIS assumes qgisMaximumVersion at 1.999. > > Does this mean that 2.0+ compatible plugins will always need to set > a qgisMaximumVersion ? Or will plugin manager be smart enough to assume > an higher max if qgisMinimumVersion=2.0 ? > > --strk;
It's all described in my reply to Nathan's mail (Monday, 15:46 CEST). To be precise: if not explicitly set, the default value is: qgisMaximumVersion = floor( qgisMinimumVersion ) + ".99.99" So you *only* need to set qgisMaximumVersion, if you're not satisfied with the defaulf range x.y - x.99.99 Can we put it somewehere to the docs? I was writting it a dozen times again and again since this behaviour had been introduced right before 1.0 release :D _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
