Re: Bonobo bug: can't set status to empty string
- From: Michael Meeks <michael helixcode com>
- To: Maciej Stachowiak <mjs eazel com>
- Cc: Miguel de Icaza <miguel helixcode com>, John Sullivan <sullivan eazel com>, gnome-components-list gnome org
- Subject: Re: Bonobo bug: can't set status to empty string
- Date: Fri, 13 Oct 2000 09:42:44 -0400 (EDT)
Hi,
On 12 Oct 2000, Maciej Stachowiak wrote:
> Miguel de Icaza <miguel helixcode com> writes:
> > I am not sure we even want to support the broken push/pop concept for
> > status bars, btw.
>
> I agree. Push/pop adds complexity and not a lot of benefit.
Me too. Which is why we don't support push pop as such. What we do
support is a per component push / pop type effect so that if we have this
sequence:
Component Action Status
A set to Foo Foo
B set to Baa Baa
B set to "" or NULL Foo
A remove ""
This seems to me to be the most logical and consistant way of
sharing the status bar between multiple components. The way it is
implemented uses one statusbar id per component ( and 1 for tooltips
). There is no 'push / pop' action visible in the API.
FWIW the statusbar structure made this very easy.
Regards,
Michael.
--
mmeeks gnu org <><, Pseudo Engineer, itinerant idiot
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]