[Mono-osx] PermFormSelectOnMainThread patch for monomac
kjpou at pt.lu
Tue May 24 05:11:35 EDT 2011
You are absolutely correct about the assuming not-null but there is no
way of knowing up front if a null value is valid or not unless you are
very familiar with the wrapper code that is being written.
The automatic parser that Miguel wrote, which I think most people use,
takes a header file and outputs automatically the interface wrapper for
inclusion into the system. Doing it by hand is very, very time
consuming. It is then necessary to tweek it by hand. One of those
tweeks is for [Null Allowed] value which you have to add by hand for
On 5/24/11 12:17 AM, Lee V. Andrus wrote:
> Most wrapper methods in MonoMac assume or require that all class parameters
> are not null--including many for which null is an acceptable (and sometimes
> necessary) value.
> Maxi Combina wrote:
>> My selector does not take argument, so I use null as argument...
>> and InvokeOnMainThread() fails. If I change
>> monomac/src/Foundation/NSObject.cs:InvokeOnMainThread() to check for null,
>> it works.
>> So: could this small change be added? Or is it mandatory to pass a
>> paramter to InvokeOnMainThread()?
> View this message in context: http://mono.1490590.n4.nabble.com/PermFormSelectOnMainThread-patch-for-monomac-tp3543684p3545677.html
> Sent from the Mono - OSX mailing list archive at Nabble.com.
> Mono-osx mailing list
> Mono-osx at lists.ximian.com
More information about the Mono-osx