Do you mean the user would have to manually set back the version number when they compile?
That does sound like a bitter pill to swallow. Setting internal variables sounds much more palatable to me. I'll create an internal bool handleShiftAsSoftReturn which will default to true. Makes sense? Harbs On Aug 31, 2013, at 3:01 AM, Alex Harui wrote: > > > On 8/30/13 4:58 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: > >> Hi, >> >> Would a check on the SDK version number be a better way to handle this? > That was Adobe policy, but it meant you had to go back to old code paths > for any other paths changed in that version as well. IMO, that was too > big a pill to swallow for some. But yes, Harbs can choose that if he > wants. > > -Alex >
