Hello and welcome,

Like you I found it by coincidence about a month ago. I believe that since cocoa# is bundled with osx-mono people just asume that it's the the only alternative and don't know about monobjc yet ...

I would not call it "promising" though... It's quite complete and useful today.

Regards,
Johan Kullbom

1 jun 2008 kl. 08.24 skrev Jérôme Gagnon-Voyer:

Forget it, I was totally wrong!

                        textUserID.StringValue="Jerome";

This was the right thing to do.

But I do have another questions...How could I have never heard of monobjc before? Is it quite new? Because it looks very promising. The documentation is complete, it seems easy to bundle mono with your application, support for a lot of librairies. Why is everybody using cocoa# ?


Jérôme
[EMAIL PROTECTED]




On May 31, 2008, at 11:10 PM, Jérôme Gagnon-Voyer wrote:

Hi guys, that may be a basic question but I'm just beginning with Monobjc. I was using CocoaSharp before.

So I've got in my interface a NSTextField and a Button.

      [ObjectiveCField]
                public NSTextField textUserID;

  [ObjectiveCMessage("loginButton:")]
        public void LoginButton(Id sender)
        {
                                
                        textUserID.SetValueForKey("Jerome","textUserID");
        }

In interface builder: loginButton is a class action of my class Hello Controller and textUserID is a Class Outlet of Hello Controller.

What I'm trying to do, is to change the value of the textUserID when the user press the Login button. But the NSTextField never change value. I know the LoginButton function is executed but I'm really not sure how the "SetValueForKey" is working.

Can you help me? Thanks!

Jérôme
[EMAIL PROTECTED]






Reply via email to