Open julapy opened 10 years ago
hm, I thought we don't put new (non-critical) issues into milestones close to release? I'm pushing this back to 0.9.1. (doesn't mean it can't be finished/merged before, though)
as far as I can tell it is fairly critical. the framework we're using has been deprecated for a while now and OF doesn't build now if the minOS is set to 6.0 ( something we're not currently doing, but someone using OF might reasonably want to do ).
It would be good for us to move to CoreMotion for the short time both are still supported so we can deprecate nicely.
@julapy - does that sound right? correct me if I am wrong on this.
In the PR this came from (#3217), Lukasz states that UIAccelerometer has been deprecated in 5.0 (correct as far as I found), and the PR description implies to me that OF still works in 6.0 (with that PR), so apparently we can still use it in 6.0. Someone on the internet says he still gets a warning for 7.0, so I think we still have quite some time. Conversely, @danoli3 states he gets an error with 6.0, but maybe he meant "warning" not "error"?
Also, not really familiar with our iOS internals, but do we really have to deprecate something in OF, i.e. is this move to CoreMotion not something which is hidden behind our API anyway?
All good points/questions :) I’ll let @julapy answer as I may be understanding it wrong! =
UIAccelerate has become deprecated. CoreMotion is needed for ofxiOS.
looking at https://github.com/trentbrooks/ofxCoreMotion for the job. @trentbrooks, feel free to insert some wisdom here :)