weird parent/child behavior in wxOSX-Cocoa, 2.9.4.1

wxPython Users
1

In the latest version of wxPython 2.9, a child Frame now follows its
parent Frame when the latter is moved around on the screen. Several
of my users have complained about this; is there any way to disable
this other than not setting the parent of the child in the first
place? Unfortunately I think some of my code may depend on the parent
being defined and I'm hesitant to invest the time fixing this.

Sorry if this has been discussed before, I didn't find anything
googling. I've attached a runnable example (this is on OS 10.7.5, if
it matters).

thanks,
Nat

wx_parent_test.py (864 Bytes)

2

Yeah, I find it annoying too. I asked about this on wx-dev a few months ago, the thread is here: https://groups.google.com/d/topic/wx-dev/fqJvnYrUYIs/discussion

So apparently it sounds like this is the native way that parent/child windows are supposed to behave on OS X.

···

On 12/1/12 8:35 AM, Nat Echols wrote:

In the latest version of wxPython 2.9, a child Frame now follows its
parent Frame when the latter is moved around on the screen. Several
of my users have complained about this; is there any way to disable
this other than not setting the parent of the child in the first
place? Unfortunately I think some of my code may depend on the parent
being defined and I'm hesitant to invest the time fixing this.

Sorry if this has been discussed before, I didn't find anything
googling. I've attached a runnable example (this is on OS 10.7.5, if
it matters).

--
Robin Dunn
Software Craftsman

3

Ah, I hadn't noticed that. It means that the behavior has been changed in 2.9.5, and that's good news.

Thanks for pointing it out.

···

On 12/4/12 1:30 AM, CMcP wrote:

On Tuesday, 4 December 2012 01:02:18 UTC, Robin Dunn wrote:

    On 12/1/12 8:35 AM, Nat Echols wrote:
     > In the latest version of wxPython 2.9, a child Frame now follows its
     > parent Frame when the latter is moved around on the screen. Several
     > of my users have complained about this; is there any way to disable
     > this other than not setting the parent of the child in the first
     > place? Unfortunately I think some of my code may depend on the
    parent
     > being defined and I'm hesitant to invest the time fixing this.
     >
     > Sorry if this has been discussed before, I didn't find anything
     > googling. I've attached a runnable example (this is on OS
    10.7.5, if
     > it matters).

    Yeah, I find it annoying too. I asked about this on wx-dev a few
    months
    ago, the thread is here:
    https://groups.google.com/d/topic/wx-dev/fqJvnYrUYIs/discussion
    <https://groups.google.com/d/topic/wx-dev/fqJvnYrUYIs/discussion&gt;

    So apparently it sounds like this is the native way that parent/child
    windows are supposed to behave on OS X.

Interestingly, although the effect is as described with Classic
wxPython, with Phoenix the parent and child frames can be moved
independently. (wxPython-Phoenix-r73087-darwin-py3.2 on Mac OS X 10.8.2).

--
Robin Dunn
Software Craftsman