realbasic-nug
[Top] [All Lists]

Re: win32 tip about invisible controls

To: REALbasic Network Users Group <realbasic-nug at lists dot realsoftware dot com>
Subject: Re: win32 tip about invisible controls
From: David Grogono <dave at realsoftware dot com>
Date: Wed, 30 Jan 2002 11:53:45 -0600
on 1/30/2002 10:43 AM, Matthias Buercher at reader at belle-nuit dot com wrote:

> i wanted just to share a tip:
> i am about to adapt my textfilter program to windows and i had problem
> when i change between an editfield and a listbox in runtime. the
> editifield and the listbox share the same space and are visible
> alternatively.
> in win32, they shouldn't. i have not been able to make the listbox
> visible, when it is unvisible at the beginning.
> the workaround is easy: just move the listbox one pixel to the left and
> they will not share exactly the same space any more and it works like
> vanilla.
> therefore: two controls should not share exactly the same position and
> size in win32.

Hi Matthias -

What you are finding is that one of your controls is ending up as a "child"
of the other control.  Once this happens setting the visible property of the
parent also affects the child.  Although this can be useful at times as you
noticed it only happens on win32 builds.  In 4.5 we will likely add this
same feature (parent/child relationship) for Mac targets as well.  We also
hope to offer a way to break this relationship for situations like yours
where it's not desired behavior.

> now, if someone could explain to me why a SDI application sometimes not
> stops its process after exiting...

You have probably allowed the last window to close without quitting the app.
On the Mac this will leave you with no open windows but a visible menubar.
On an SDI app the menu disappears when the window closes.  You may be able
to solve it for your app by quitting in the window close event.

--
David Grogono
dave at realsoftware dot com



<Prev in Thread] Current Thread [Next in Thread>