Re: [Pythoncard-users] Question about child-window, dialog z-order

[<bra...@om...>]

I've seen this same symptom on the Mac--it doesn't seem to happen on 
Windows, which explains why Alex hasn't see this problem.

To avoid the flicker problem, I usually uncheck "Visible at Startup" in 
the Background Info dialog in resource editor for a child window, and then 
explicitly set self.visible=True right before the self.Raise() statement.

Liame Clarke wrote on 06/08/2005 01:20:02 AM:

> Hey man,
> 
> At the end of your method which calls the dialog box i.e. 
> 
> def foo(self, event):
>     <some stuff>
>      <dialog is called>
>      <Dialog has finished, now call...>
>      self.Raise()
> 
> Try it, it may flicker, however.

> On 6/8/05, kim...@ya... < 
kim...@ya...
> > wrote:
> Hello list,
> 
> I am writing an app involving child-window.  When the 
> child window invokes a dialogbox, it switches focus to
> the main windows first, before poping up. Of course,
> when it closes, the child-window becomes underneath
> the main window.
> 
> Is there a parameter I am suppose to set or something 
> in order to maintain the proper z-order?
> 
> Thanks,
> 
> --
> John
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you 
shotput 
> a projector? How fast can you ride your desk chair down the office luge 
track?
> If you want to score the big prize, get to know the little guy.
> Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
> _______________________________________________
> Pythoncard-users mailing list
> Pyt...@li...
> https://lists.sourceforge.net/lists/listinfo/pythoncard-users
> 
> 
> 
> -- 
> 'There is only one basic human right, and that is to do as you damn 
> well please. 
> And with it comes the only basic human duty, to take the consequences.'