wxCocoa no top menu

wxPython Users
1

Hi Guys,

I am a co-developer of the S2 statistics program
at Google Code Archive - Long-term storage for Google Code Project Hosting.

I finally dragged myself kicking and screaming into the current
millennium, and loaded Macports py27-wxpython-devel 2.9.4. on my
Mountain Lion machine. I was previously using a 32 bit Carbon based
approach which worked fine.

If I now do a

frame.Show()

I get my program in a frame in the middle of the screen, and the usual
top of screen menu. If I click the green LED, it resizes to take up
most of the screen as expected. However, if I do

frame.ShowFullScreen(True,False)

I get the frame full screen, and I get the toolbar, but not the title
bar with the 3 LEDs or the top menu.

Has anyone else come across this behaviour? Is this a bug, my
misunderstanding, or the way it works?

I guess I could set the frame size to wx.DisplaySize() before showing
it, but that seems messy unless it is the wxCocoa way of doing things?

I think you are misunderstanding what ShowFullScreen does. See wxWidgets: wxTopLevelWindow Class Reference

Perhaps you are wanting the Maximize method? wxWidgets: wxTopLevelWindow Class Reference

As a second question, are there any sites which deal with issues of
moving from Carbon to Cocoa under wxPython?

There may be a few things in the wiki. What kind of problems have you run in to? Were you using a 2.9.x Carbon build before or was it 2.8.12.1?

···

On 8/15/12 5:49 PM, Mark Livingstone wrote:

--
Robin Dunn
Software Craftsman

2

Hi Robin,

Thanks for the speed reply!

···

On Thursday, 16 August 2012 11:13:20 UTC+10, Robin Dunn wrote:

On 8/15/12 5:49 PM, Mark Livingstone wrote:

Has anyone else come across this behaviour? Is this a bug, my

misunderstanding, or the way it works?

I guess I could set the frame size to wx.DisplaySize() before showing

it, but that seems messy unless it is the wxCocoa way of doing things?

I think you are misunderstanding what ShowFullScreen does. See
http://docs.wxwidgets.org/trunk/classwx_top_level_window.html#ab4089f1274bcb74e5f7763d1fb84ee28

Perhaps you are wanting the Maximize method?
http://docs.wxwidgets.org/trunk/classwx_top_level_window.html#addb1612e9f00ac82c2e19c2bac6ffc4f

Thanks, I will read up on that.

As a second question, are there any sites which deal with issues of

moving from Carbon to Cocoa under wxPython?

There may be a few things in the wiki. What kind of problems have you
run in to? Were you using a 2.9.x Carbon build before or was it 2.8.12.1?

Previously I was using Carbon 2.8.12.1 so maybe things worked differently then?

At present, this Maximise issue is the only one I have noticed when going from Carbon to Cocoa. Everything else “just works” :slight_smile:

My second question was mostly geared towards wondering if there were any other issues I may face that are not immediately apparent, and what other “goodness” Cocoa may bring that I can consider using when doing the 2.8 Carbon to 2.9 Cocoa move. I’ll check the Wiki again!

Since I am working towards our first OS X release, now is the time to break things if it means improvements can be made - before I get any other users :wink:

Cheers,

MArkL

3

There may be a few things in the wiki. What kind of problems have you
run in to? Were you using a 2.9.x Carbon build before or was it 2.8.12.1?

Previously I was using Carbon 2.8.12.1 so maybe things worked differently then?

At present, this Maximise issue is the only one I have noticed when going from Carbon to Cocoa. Everything else “just works” :slight_smile:

My second question was mostly geared towards wondering if there were any other issues I may face that are not immediately apparent, and what other “goodness” Cocoa may bring that I can consider using when doing the 2.8 Carbon to 2.9 Cocoa move. I’ll check the Wiki again!

Since I am working towards our first OS X release, now is the time to break things if it means improvements can be made - before I get any other users :wink:

Cheers,

MArkL

Well for one thing, Cocoa adds 64-bit support on Mac. Other than that, there are several new wxPython widgets in 2.9, such as webview and the various DataViewCtrls, among several others.

  • Mike
4

If ShowFullScreen was working like Maximize in 2.8.12.1 then ShowFullScreen was broken.

···

On 8/15/12 6:26 PM, Mark Livingstone wrote:

Hi Robin,

Thanks for the speed reply!

On Thursday, 16 August 2012 11:13:20 UTC+10, Robin Dunn wrote:

    On 8/15/12 5:49 PM, Mark Livingstone wrote:

     > Has anyone else come across this behaviour? Is this a bug, my
     > misunderstanding, or the way it works?
     >
     > I guess I could set the frame size to wx.DisplaySize() before
    showing
     > it, but that seems messy unless it is the wxCocoa way of doing
    things?

    I think you are misunderstanding what ShowFullScreen does. See
    wxWidgets: wxTopLevelWindow Class Reference
    <wxWidgets: wxTopLevelWindow Class Reference;

    Perhaps you are wanting the Maximize method?
    wxWidgets: wxTopLevelWindow Class Reference
    <wxWidgets: wxTopLevelWindow Class Reference;

    Thanks, I will read up on that.
     >
     > As a second question, are there any sites which deal with issues of
     > moving from Carbon to Cocoa under wxPython?

    There may be a few things in the wiki. What kind of problems have you
    run in to? Were you using a 2.9.x Carbon build before or was it
    2.8.12.1?

Previously I was using Carbon 2.8.12.1 so maybe things worked
differently then?

--
Robin Dunn
Software Craftsman