A couple of questions regarding pathMajorRadius

Hi there!


I have a couple of questions for you, regarding the property pathMajorRadius that can be obtained through UITouch.valueForKey.

I noticed this property doesn't provide accurate size values but rather wired values at certain intervals... What I want to know is if there's a more precise way to get the touch size aside from pathMajorRadius, and additionally, what is the maximum value pathMajorRadius can return, which I need in case there's no better option to work with than this property.


Thanks in advance!


Manu

UITouch has no such property, so I guess you mean "majorRadius".


Have you actually looked at the class reference documentation?


https://developer.apple.com/library/ios/documentation/UIKit/Reference/UITouch_Class


It describes majorRadius and majorRadiusTolerance. Note that it says these are the values "returned by the hardware", so it seems unlikely you'll get anything better elsewhere.

Thank you! Actually, UITouch does have the pathMajorRadius property but you need to get it thru the valueForKey function, but I think I'm going to start using majorRadius instead which is basically the same value.


That being said, what about majorRadius' maximum value? Can you help me with that?


Regards,

>> Actually, UITouch does have the pathMajorRadius property


Where is "pathRadiusMajor' documented? If it's not documented, you should probably not be using it.


>> what about majorRadius' maximum value?


That was the point of sending you to the documentation. For 'majorRadiusTolerance' it says:


Discussion

This value determines the accuracy of the value in the majorRadius property. Add this value to the radius to get the maximum touch radius. Subtract the value to get the minimum touch radius.


I don't know if that's the kind of "maximum" you're asking about, but that's the information it gives you.

Sorry dude but you are not even trying to help here. Thanks for nothing.

Huh? According to the documentation, the hardware accuracy of the touch places it between:


majorRadius - majorRadiusTolerance


and:


majorRadius + majorRadiusTolerance


That's the minimum and maximum. Isn't that what you asked for?

Sounds more like he was looking for more private APIs he could (ab)use. Because it's always more exciting when your app gets rejected and/or fails badly at some random time in future or on a device you didn't test when the private implementation changes.

A couple of questions regarding pathMajorRadius
 
 
Q