OO names/references from perspective of code

[true911m]

This gets to the core of my most frustrating lack of understanding at the moment, and now I have an example to illustrate it. It may get long-winded, but I'm trying to figure out how to describe it somewhat briefly.

I'm using Boa to reconstruct a simple VB app I'm familiar with, so some of the generated naming should be familiar.

My app has two windows. The first opens to ask for user information. Fill it in, and press a button for generated password results, which pop up in a second window.

As I understand it, in code:

Filename is App1.py
Class is BoaApp
Instance of BoaApp is 'application'
application creates first window:

class BoaApp(wx.App):
    def OnInit(self):
        wx.InitAllImageHandlers()
        self.main = Frame1.create(None)        
        self.main.Show()
        self.SetTopWindow(self.main)
        return True

Now, the user fills in info and presses btnGenerate, an event in Frame1.py (now instantiated as 'main')

My btnGenerate handler (inside Frame1) hides the input window, and creates the 'results' window:

def OnBtnGenerateButton(self, event):
        self.Hide()
        results = Frame2.create(None)
        results.Show()

The results window has another button, btnAnother, to allow the user to go back and enter info for another user.

I know what I want to do at this point. I want to hide 'results', show 'main', and destroy 'results' (because 'main' creates a new 'results' each time its button is pressed).

What I can't figure out, from the perspective of the event handler in 'results', is how to reference the name of the hidden Frame1/'main' window to tell it to Show().

My understanding of the hierarchy of the instantiated classes would have me use 'application.main.Show()', based on the names of the instantiated classes, but that doesn't work; nor do dozens of combinations of "self, App1, main, BoaApp, results, parent" or any other pertinent labels I can come up with in my desperation.

I thought I understood the conceptual hierarchy of OO, but I'm either missing something really basic, or my practical interpretation is flawed, or both/worse.

I hope this is enough description to understand exactly what is my point of misunderstanding here. I've been hesitating posting because I didn't want to start a very long back-and-forth of answers not pertaining to a problem I haven't described well enough.

Thanks for reading.

[bartonc]

This gets to the core of my most frustrating lack of understanding at the moment, and now I have an example to illustrate it. It may get long-winded, but I'm trying to figure out how to describe it somewhat briefly.

I'm using Boa to reconstruct a simple VB app I'm familiar with, so some of the generated naming should be familiar.

My app has two windows. The first opens to ask for user information. Fill it in, and press a button for generated password results, which pop up in a second window.

As I understand it, in code:

Filename is App1.py
Class is BoaApp
Instance of BoaApp is 'application'
application creates first window:

class BoaApp(wx.App):
    def OnInit(self):
        wx.InitAllImageHandlers()
        self.main = Frame1.create(None)        
        self.main.Show()
        self.SetTopWindow(self.main)
        return True

Now, the user fills in info and presses btnGenerate, an event in Frame1.py (now instantiated as 'main')

My btnGenerate handler (inside Frame1) hides the input window, and creates the 'results' window:

def OnBtnGenerateButton(self, event):
        self.Hide()
        results = Frame2.create(None)
        results.Show()

The results window has another button, btnAnother, to allow the user to go back and enter info for another user.

I know what I want to do at this point. I want to hide 'results', show 'main', and destroy 'results' (because 'main' creates a new 'results' each time its button is pressed).

What I can't figure out, from the perspective of the event handler in 'results', is how to reference the name of the hidden Frame1/'main' window to tell it to Show().

My understanding of the hierarchy of the instantiated classes would have me use 'application.main.Show()', based on the names of the instantiated classes, but that doesn't work; nor do dozens of combinations of "self, App1, main, BoaApp, results, parent" or any other pertinent labels I can come up with in my desperation.

I thought I understood the conceptual hierarchy of OO, but I'm either missing something really basic, or my practical interpretation is flawed, or both/worse.

I hope this is enough description to understand exactly what is my point of misunderstanding here. I've been hesitating posting because I didn't want to start a very long back-and-forth of answers not pertaining to a problem I haven't described well enough.

Thanks for reading.

This is (roughly) how I do this:

In main

def __init__(self, prnt):
    self.results = None
 
def OnBtnGenerateButton(self, event):
    if self.results is None:   # update the value of self.results
        self.results = Frame2.create(self)   # give Frame2 a link back to the creator
    else:
        self.results.InitWidgets()   # main created it ONLY main should destroy it
    self.results.Show()

In Frame2

def __init__(self, prnt):
    self.parent = prnt  # keep the link back for later
 
def InitWidgets(self):
    pass    # put widgets in some initialized state
 
def OnDoneButton(self):    # the event handler
    self.Hide()
    self.parent.Show()

[true911m]

This is (roughly) how I do this:

In main
[code]
def __init__(self, prnt):
self.results = None
...

I played around with this a little and got my multi windows working. I see what I was doing wrong, is that where I created the frame with 'None', that is the place where you're passing the parent's identity, so use 'self' instead. Then inside the created instance, store 'parent' while in the init method for later use.

I also left the window alive instead of destroying it each time; this lets the users move it around, and it stays where they left it when it pops up again.

I didn't see a real need for the Widgets.init each time I reopened, partly because of that last paragraph. Maybe it makes sense when things get more complex -- not there yet.

[bartonc]

I played around with this a little and got my multi windows working. I see what I was doing wrong, is that where I created the frame with 'None', that is the place where you're passing the parent's identity, so use 'self' instead. Then inside the created instance, store 'parent' while in the init method for later use.

I also left the window alive instead of destroying it each time; this lets the users move it around, and it stays where they left it when it pops up again.

I didn't see a real need for the Widgets.init each time I reopened, partly because of that last paragraph. Maybe it makes sense when things get more complex -- not there yet.

Yep. Sounds like you've got a handle on it now.
I threw in the initWidgets in case you were destroying it in order to re-create it with constructor values.