<DIV>
<DIV>one more question... I think I have a problem with my globals, I have some constants that I use throughout my application; however they do not work, I receive error messages that the "global is not defined", it is defined, which makes me think I defined it in the wrong place. where do you put globals? you say the "file level," could you be more specific? I have one script per dialog/frame, do I need to redefine the globals for each frame and dialog, shouldn't I be able to place them in the application file and have the globals available for each frame and dialog? </DIV>
<DIV> </DIV>
<DIV>thanks.</DIV>
<DIV> </DIV>
<DIV>Jeff<BR><BR><B><I>Alan Gauld <alan.gauld@blueyonder.co.uk></I></B> wrote:</DIV>
<BLOCKQUOTE class=replbq style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #1010ff 2px solid"><BR>> Hello, I have an application I am writing with wxpython and the<BR>> boa constructor.<BR><BR>Dunno anything about Boa so that might invalidate my reply...<BR><BR>> I am unsure how to "talk between frames and dialogs".<BR>> Global variables don't seem to be passed into child dialog<BR>> and other frames from the parent frame,<BR><BR>Global variables exist at the file level and should be visible within<BR>any function within that file. However global variables are almnost<BR>certainly the wrong answer! :-)<BR><BR>> I am unsure as to how to get a value from a control in the parent<BR>> dialog from the child dialog.<BR><BR>Just to be clear, we are talking about GUI control here not<BR>class inheritance or widget containment?<BR>ie You have a dialog whereby you hit a button and a new "child"<BR>dialog opens?<BR><BR>><BR>> myValue =
self.textCtrl2.GetValue()<BR>><BR>> but what if the above line is in a different dialog or frame<BR>> than the text field?<BR><BR>If its in a different object then one of two situations arises:<BR><BR>1) If you know the new dialog needs to know it you pass a refernce<BR>to the parent dialog into the child dialog constructor when you<BR>call it. The child dialog can then call<BR><BR>parent.textCtrl2.GetValue()<BR><BR>OR<BR><BR>2) If the parent needs to know the value from the child dialog you<BR>return it as a result. Without knowing more about the design of your<BR>application its hard to be definite.<BR><BR>But one thing you should never be doing is mixing up GUI widget<BR>code and application logic... So if its an application object that<BR>needs to know then pass a reference to the app object to the dialog<BR>or a reference to the dialog to the app (latter is best for reuse).<BR><BR>HTH<BR><BR>Alan G.<BR><BR></BLOCKQUOTE></DIV>