[Wxruby-dev] Various OS X issues (was: OS X 10.2.6 compile error)

[Kevin Smith]

On Fri, 2003-07-18 at 10:35, John Platte wrote:
> >> nothing.rb works perfectly.
> >
> > Hooray. So even the menus look ok, and function properly?
> 
> No menu, and it doesn't come to the front until I click it. But I don't 
> get burps or bad behavior.

Oh, right. nothing.rb has no menu. Does minimal.rb (with the icon stuff
commented out) show a menubar?

> It's looking like my hunch is right. The Mac seems to need some special 
> TLC to get menus working. Look at this thread from the wxPython list:
> 
> http://lists.wxwindows.org/archive/wxPython-mac/msg00052.html

Indeed. Unfortunately, that will require someone with knowlege of (and
access to) OS X to code and debug.

> And I'm not sure what part of this information might be relevant:
> 
> http://wiki.wxwindows.org/wiki.pl?WxMac_Issues

It certainly seems to describe some of the icon problems we've been
having. Aside from that, it seems to deal more with how to go above and
beyond basic functionality, rather than how to get a simple app working.
Good reference for the future, though.

> The important bit for me/us is that this is harmless. I suspected so, 
> but it's confirmed. Maybe it should be a Mac FAQ, though, since 
> presumably other developers will run into this.

Mac FAQ. Great idea. Should we put most content on the wiki, and just
point there in the README, or should we actually try to have
platform-specific FAQ files as part of our release? For now, I vote for
the former, because it will be less work!

> >     evt_enter_window {puts('Mouse in')}
> >     evt_leave_window {puts('Mouse out')}
> >     evt_left_down {puts('Mouse down')}
> >     evt_idle {puts('Idle')}
> 
> No complaints...just many lines that say "Idle". I entered the window, 
> clicked in the window, left the window, etc etc etc...

Ok. So we are getting idle messages, which means callbacks from
wxWindows to wxRuby are working. And we're in some kind of message loop
that knows we're idle. That's all good.

But you never saw any of the other messages, right? That certainly is
consistent with the behavior you're seeing that wxRuby apps are not
getting any input events/messages from the OS. I wonder why that would
be. Did you say you had tried the C++ wxWindows samples and they worked
ok?

Kevin