def Back_Button(self, event):
print "Indicator From Diagnostic"
if self.indicators_frame is None:
self.indicators_frame = DiagnosticIndicators()
self.indicators_frame.Show()
self.Hide()
So the first time the button is pressed, the frame is created,
but subsequent presses returns the same frame.
--
You received this message because you are subscribed to the Google Groups "wxPython-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to wxpython-user...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
@ torsten : the wizard class seems to be to sequential, as in next and back control, my ap seems to be more random access, maybe they go from window one to window 3 and then back to window one to window 5, and so on from what i read the wizard class goes window one, window 2 window 3
If your screen is so small it is likely that each TopLevelWindow (i.e. each frame) takes up the whole screen. Then Raise() is fine. However if there are frames that do not fill the entire screen then when those smaller frames are on top you will see full size frames behind it. This could cause visual confusion (especially on a small screen). Then Hide() might be betterif button1:frame1.Show()frame2.Hide()frame3.Hide()
sadly.. or maybe wisely I am beginning to see this as correct simple because the event handler can be all in one place neater shorter code.. arg. recoding. lol. and with the new job I got yesterday it's gonna be a minute. maybe sometime this week. I'll be sure to report back when I blow it up.
--
You received this message because you are subscribed to a topic in the Google Groups "wxPython-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/wxpython-users/alidSRya9tI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to wxpython-users+unsubscribe@googlegroups.com.