You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This would crash out the app. Digging around we saw an error in the console indicating it could not convert an NSNumber to a @.
I think there is a bug in the Operation.h code. The applyToObject: and castNumber:toType:intoBuffer: methods appear to assume that if the passed argument is a NSNumber, then the type on the target method will be a primitive type. However with the touch:y: method the arguments are NSNumber objects. This causes castNumber:toType:intoBuffer: to through an error.
I think some code needs to be added to check that if the target argument type is a NSNumber object, then the passed in NSNumber can just be passed through.
For the moment we are getting around this by adding quotes so that the numbers are seen as strings like this:
We have been experimenting with calling the touchx:y: category method on a UIVIew from the frank console. The command we used was this
This would crash out the app. Digging around we saw an error in the console indicating it could not convert an NSNumber to a @.
I think there is a bug in the Operation.h code. The
applyToObject:
andcastNumber:toType:intoBuffer:
methods appear to assume that if the passed argument is a NSNumber, then the type on the target method will be a primitive type. However with thetouch:y:
method the arguments are NSNumber objects. This causescastNumber:toType:intoBuffer:
to through an error.I think some code needs to be added to check that if the target argument type is a NSNumber object, then the passed in NSNumber can just be passed through.
For the moment we are getting around this by adding quotes so that the numbers are seen as strings like this:
The text was updated successfully, but these errors were encountered: