Subject: Re: [linux-audio-dev] Re: LADSPA GUI [was: New LADSPA Version - Issues Resolved?]
From: Paul Barton-Davis (pbd_AT_Op.Net)
Date: pe maalis 10 2000 - 18:51:20 EST
In message <20000310231235Z8177-287+3213_AT_nic.funet.fi>you write:
>>Juhana, it seems that you might not know GTK or X too well. This is
>>all handled quite normally unless you happened to have an input device
>>(mouse etc.) that generated X events a lot faster than anything I know
>>of.
>
>Ok, what I really meaned is that if I'm playing several waves at the same
>time in the wave editor and if all of them are auto-scrolled, then
>there should be some way to organize all GUI tasks so that level meters
>updates are served first and waveform graphing is skipped if necessary.
OK. However, what you're describing sounds close to what someone here
recently "useless pixmap updates". I am not sure that I see it that
way, but I think that in general, presenting more than one "real time"
meter or other changing display at a time is rather counterproductive.
>Yep, I'm turning my wave editor to multi-threaded system so that GUI has
>as fast as possible routines. Events are just quickly sent to elsewhere.
>Graphing is done elsewhere and only pixmap copy is done at GUI.
Exactly.
>I'm also thinking a complex GUI written with Gtk could slow down the
>system: too many configure events etc. Would it be better to have one
>drawing area where to buttons etc. are drawn?
There are no more events in GTK than in any other X toolkit. There
*might* be more overhead associated with each event, but in general, I
have not found this to be true, and even if it is, its miniscule. The
key thing to remember that doing anything in the GUI more than 100
times a second is completely and utterly pointless. This is really
important.
--p
This archive was generated by hypermail 2b28 : su maalis 12 2000 - 09:14:06 EST