>> I see it as a feature rather than a fix, as it addresses a lack of >> functionality rather than a incorrect functioning. > > Just to be clear, I am adding an option to enable the old mibile skins > which have been around 4.6.
OK, I must have misunderstood. Let me summarize how I understand this after reading your last email, and re-reading some previous ones and looking at the commit: The new mobile skins 'overrule' the old skins, currently without an option to go back to the way it was. This means that people who rely on the old skins now have to go into their app and make changes. Your fix reduces these changes to just adding compiler arg, that then instantiates a class that tricks the version check to 'read' the current platform as an older version. That sounds like a fix to me, that will prevent users of 4.14 not having the option to use the legacy skins which their apps may rely on. You may proceed ;-) Without carrying the extra commits! > On a larger point, what is the point of asking users to test the nightlies > if we are only going to fix things in the next release? The point of asking people to test is to make sure that we're releasing a stable and good quality SDK, without any regressions or new blocking bugs. Everything else is regular development, takes place on 'develop' and unfortunately must wait for the next release. Which does nothing to diminish the value of the contribution of testers whose bugs are not fixed in the current release, as they will be a valuable contribution to the next one. EdB -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
