On Tue, September 28, 2010 6:31 am, Paul Davis wrote: > On Tue, Sep 28, 2010 at 7:00 AM, Olivier Guilyardi <[email protected]> > wrote: > >> I'm not a gtk engine wizard, but the problem is still here IIUC. > > Most custom widgets for GTK suffer from this problem. Its not a new > thing. The GTK docs and even the GTK "team" have never really > advocated that all widgets should draw themselves with gdk_draw_*(), > at least not to an extent that has resulted in this being the case. > The problem is that there really is a conflict here: > > On the one hand: > > 1) the desire for a generic, powerful graphics language/API to > draw widgets with (e.g. Cairo) > > and on the other > > 2) the desire to push all widget drawing through a themeable > layer which necessarily reduces the complexity of the graphics API > (e.g. gdk_draw_*()) > > I don't think that these can be reconciled. >
I have to agree. The latter is for quick generic ui development and the former is for those who are more technically inclined or have a specific/unique concept they are tasked with presenting. IMO a better generic widget to save space and allow for knob like interaction would be a vertical/horizontal wheel. Something like a mouse wheel would work. It would also be much easier to draw and would scale well too. -- Patrick Shirkey Boost Hardware Ltd. _______________________________________________ Linux-audio-dev mailing list [email protected] http://lists.linuxaudio.org/listinfo/linux-audio-dev
