FiveTech Support Forums

I have Dialog A, which calls Dialog B. When B opens, I want to hide A.

In the past, I simply made the object for Dialog A private, and when it called B, I could use a Hide command:
PRIVATE oDlgA
And in the second one:
oDlgA:hide()

Now, however, I am moving everything to classes, and so oDlgA is logged as DATA. When I call Dialog B, oDlgA is not visible. I tried passing it as a parameter, but no success ( it isn't seen )

Is there a function in FW that allows me to see the calling ( Active ) dialog when I open the Method that will use Dialog B ?

Thanks.

It returns a numeric. So you can't use :hide()

oWdlg:hide()

cannot be replaced with

hDlg := GetActiveWindow( )
hDlg:hide()

However, this does work:

hDlg := GetActiveWindow( )
ShowWindow( hDlg, 0 ) // Hides
then
ShowWindow( hDlg, 1 ) // Shows it again in normal size

Thank you.

The manual says that does not work from dialogs

Right. Sorry.

EMG

TimStone wrote:
Now, however, I am moving everything to classes, and so oDlgA is logged as DATA. When I call Dialog B, oDlgA is not visible. I tried passing it as a parameter, but no success ( it isn't seen )

Here are the two main issues:

1) I have a function which is a pop up dialog. Windows doesn't always handle it well, so I need to use the OF to be sure it stays in focus.
2) I want to inherit the font and other values from the calling dialog, and again this is in a function.

DialogA ( oWdlgA ) is the calling routine in a class.

Dialog B ( oWdlgB ) is the popup dialog called from oWdlgA.

If I used PRIVATE in the calling routine ( PRIVATE oWdlgA ) then I could use OF oWdlgA in the creation of oWdlgB to solve problems 1 and 2,

EXCEPT:

The function may be called from many routines and we don't always know the name of the calling Dialog, and also we don't use PRIVATE in a class.

So that is what I'd like to resolve ....

Tim,

First you don't ever HAVE to use Privates. I haven't used them in 15 or 20 years. There is always a another way. Privates are always going to be a source of hard to find and seemly random errors.

So if I understand this correctly, you have a function that you call from several other places, and those places might be another function or a class? It thus seems that what you need is to have the top level dialog visible in either another function or class. So, why can't you just pass the dialog name to these other routines?

someFunction( oDlg )

or,

oSomeObject:someMethod( oDlg )

I'm guessing my assessment isn't right since I am sure you would have already tried the above.

James