Freddie Unpenstein wrote:
>> It is the trade-off of the policy that "the selected item is under
>> the pointer in the just shown popup, period." I think it is
>> generally good, but this is an example of where it shows its
>> drawbacks. However, for the sake of UI consistency, I believe it
>> s
I am pretty negative about the combo as a control, not just the GTK
combo. Widget sets don't have much of a choice but to include it since
it's considered a core control, but as a developer, I try to avoid it if
I can.
As has been discussed previously, the problem with the combo as a
control is t
David Necas (Yeti) wrote:
> On Fri, Nov 25, 2005 at 11:26:58PM +0200, Paul Pogonyshev wrote:
> >
> > It is the trade-off of the policy that "the selected item is under the
> > pointer in
> > the just shown popup, period." I think it is generally good, but this is
> > an example
> > of where it
> It is the trade-off of the policy that "the selected item is under
> the pointer in the just shown popup, period." I think it is
> generally good, but this is an example of where it shows its
> drawbacks. However, for the sake of UI consistency, I believe it
> should _not_ be changed. I.e. it be
Checkout combobutton from Gtkextra. Very flexible. I used it to put a calendar
widget in a combo. I requested it be moved into gtk. Whatever, I like it and
will continue to use it.
Kim
On Thu, 24 Nov 2005 05:55 am, control H wrote:
> [I already posted this to the gtk-list, I'm not sure which
On Fri, Nov 25, 2005 at 11:26:58PM +0200, Paul Pogonyshev wrote:
>
> It is the trade-off of the policy that "the selected item is under the
> pointer in
> the just shown popup, period." I think it is generally good, but this is an
> example
> of where it shows its drawbacks. However, for the s
control H wrote:
> > Well, I must admit that I haven't used Windows more than occasionaly
> > for the last three or four years, but the last time I checked,
> > Windows combo box was much _worse_ than GTK+'s, in my opinion. You
> > would often get a five-line combo where you'd have to scroll like
control H wrote:
> > I'm not saying GTK+'s combo is perfect, but I think it is generally better
> > than anything else I've seen. At least it always uses all the screen space
> > it has.
>
> But this is one of my other objections: it merely _tries_ to use all the
> screen
> space available. It d
> Well, I must admit that I haven't used Windows more than occasionaly for the
> last three or four years, but the last time I checked, Windows combo box was
> much _worse_ than GTK+'s, in my opinion. You would often get a five-line
> combo where you'd have to scroll like hell to skip all those 20
control H wrote:
> [snip]
>
> > To be fair, I've worked with combo controls from at least 4 different
> > widget sets and they all were horrible. Win32, GTK, Web, Borland, Java,
> > they all suck. I think as a control, the combo control is just a bad
> > concept.
>
> I'm not that negative about
[snip]
> To be fair, I've worked with combo controls from at least 4 different
> widget sets and they all were horrible. Win32, GTK, Web, Borland, Java,
> they all suck. I think as a control, the combo control is just a bad
> concept.
I'm not that negative about a combo control. After all, a go
My current project requires that I write wrappers around all common GTK
and Win32 .NET controls to give them a common functionality set. Sort
of like what wxWindows would do but much much more simple with much less
functionality.
I mention this because with the exception of the GtkComboBox contro
[I already posted this to the gtk-list, I'm not sure which list I should use]
I'll start with apologies for upcoming rant. In general I like Gtk:
I'm programming with it for a couple of years now and it's easy to
learn, reasonably fast, has many bindings, runs on windows, and is
highly themable. H
13 matches
Mail list logo
