Thanks again Russ,
As I mentioned before, the workaround I did was to add a Pushbutton just under
the Closebutton, the red button at the top left, and in its Action event I add
Close and that works for now.
If I do find the solution I will post it.
Lennox.
Russ Jones <[EMAIL PROTECTED]> wrote: Hi Lennox.
I must admit I am puzzled.
There are two ways to instantiate a window.
One is implicit; you refer to the window or something in it, and it
will be created for you.
This is the method you are using. It generally works well, but if you
have a lot of windows, it can end up being difficult to keep track of
them. In particular, a simple test to see if a particular window
already exists can end up creating one for you.
Te other is more controlled: make some named properties for the
window types you expect to use.
Then, for example, you can say w2 = new window2
You can test w2 without accidentally making a new window, and if
window2.close sets w2 back to nil, the test can make sense.
Hmm.
Maybe someone else can chime in here. :-(
Russ
On Aug 15, 2006, at 9:52 AM, Lennox Jacob wrote:
> OK Russ, I removed everything from the window, so it is now blank.
> Same result.
> So I added a new window named window2 and I call it from a
> BevelButton in the main window like this
> If Me.Caption = "Window2" then
> window2.show
> end if
> That is the same way I call many other windows but some works
> perfectly and others don't.
> Any other suggestions?
> Thanks.
> Lennox.
_______________________________________________
Unsubscribe or switch delivery mode:
Search the archives of this list here:
---------------------------------
Do you Yahoo!?
Get on board. You're invited to try the new Yahoo! Mail Beta.
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
