Est-ce que je reçois des lectures d'accéléromètre plus précises ou plus rapides avec le mouvement de base?

Question

Je peux utiliser cette méthode du cadre de mouvement de base:

- (void)startAccelerometerUpdatesToQueue:(NSOperationQueue *)queue withHandler:(CMAccelerometerHandler)handler

comme alternative au

- (void)accelerometer:(UIAccelerometer *)accelerometer didAccelerate:(UIAcceleration *)acceleration

Méthode UIACCELECELERIEDELEGATE D'UIKIT.Là, je dois spécifier la fréquence des mises à jour.Je veux obtenir des données d'accélération aussi rapidement et exactes que possible.

Core Motion est-il mon ami ici?Quelle est la fréquence des lectures que je peux attendre de cette méthode de fondement de base?La documentation n'en parle pas.

Answer 1

Edit! Now that this answer is OVER A YEAR OLD, certainly it is only of historic value. At this stage, I guess, everyone should only be using CoreMotion and that's that. Hope this historic answer it helps an history students!

---

My impression is that: CMAttitude and CMDeviceMotion give you the benefit of both the accel'r and the gyro (if the gyro is present). Whereas CMAccelerometerData is only the accel'r. (Exactly like in the old days before Core Motion.)

My impression is that the two specific advantages of CoreMotion are:

(One) the mindboggling convenience of having Quaternions and attitude given to you on a silver platter

(Two) apparently, both gyro and accel'r are used on machines with a gyro, with no extra work from you ... a huge advantage.

I believe there is no actual technical difference in the quality of usage of the accelerometer per se.

Thus: if (for some reason) you want only the accel'r, and you can do the math (if relevant to your task at hand), you could use the old-school accel'r delegate.

It seems that in short, none of us will ever again use the old-school accelerometer delegate!