Please refer to AssignValueToPointerArgument if you are overriding a method that takes a pointer as an argument.
Some methods take pointers as an argument, specified with a '*' in the method definition.
In Ruby we don't have pointers, so the following solution is provided by RubyCocoa to overcome this problem.
Say you are calling the method OSX::NSBezierPathElement#elementAtIndex_associatedPoints(index, somePoints)
The variable 'somePoints' would normally be a pointer to an array. In this case simply omit the pointer argument and the bridge will return an extra array in de results.
E.g.:
As you can see the pointer argument was omitted and the bridge returned an extra array holding the values you would normally expect to be assigned to the pointer.
Some methods take pointers as an argument, specified with a '*' in the method definition.
In Ruby we don't have pointers, so the following solution is provided by RubyCocoa to overcome this problem.
Say you are calling the method OSX::NSBezierPathElement#elementAtIndex_associatedPoints(index, somePoints)
The variable 'somePoints' would normally be a pointer to an array. In this case simply omit the pointer argument and the bridge will return an extra array in de results.
E.g.:
normal_result, extra_array = someBezierPathElement.elementAtIndex_associatedPoints(index)
As you can see the pointer argument was omitted and the bridge returned an extra array holding the values you would normally expect to be assigned to the pointer.