[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Status of NSToolbar
From: |
Quentin Mathé |
Subject: |
Re: Status of NSToolbar |
Date: |
Tue, 27 Jul 2004 16:22:10 +0200 |
Le 26 juil. 04, à 21:29, Yen-Ju Chen a écrit :
Le 26 juil. 04, à 18:28, Yen-Ju Chen a écrit :
I would like to see an example of that, but what I can said is that
currently -contentView returns a view which includes the toolbar area
when the toolbar is set; to obtain strictly the content view you need
to call -contentViewWithoutToolbar. May be the problem is here
I plan to rewrite later this implementation in order to have a
behavior which would be 100 % cocoa compatible.
I tracked down this problem with ToolbarExample.app:
if I use [toobar setVisible: NO] before [window setToolbar: toolbar],
then I can reproduce this bug.
If I reverse the order (set toolbar before set visible),
everything works O.K.
I will take a look at this problem.
Thanks.
And I try to add a view into toolbar item by -setView:
and it never shows up.
Probably your view height is higher than what is permitted by the
toolbar height.
I will look at this problem later.
But my custom view is pretty high actually,
and changes the height dynamically.
The normal toolbar is 32 pixel on Cocoa,
but there is no real limitation.
What's the limitation on GNUstep ?
This limitation exists with GNUstep because it makes the toolbar code a
lot simpler. Normally pretty high custom view can/should be avoided
because the toolbar is not here to embed complex custom view and
moreover such custom view would make display size an option without
real effect. In the future, I plan to remove this limitation but that's
not a priority now.
Quentin.
--
Quentin Mathé
qmathe@club-internet.fr