Subject: Re: [linux-audio-dev] Re: [l Re: Plug-in API progress?
From: P.J.Leonard (P.J.Leonard_AT_bath.ac.uk)
Date: ti syys 28 1999 - 08:41:56 EDT
Paul Barton-Davis wrote:
> typically, parameter updates occur because of the GUI requesting
> them. therefore, under most circumstances, the GUI does not want to be
> notified of a parameter update event - it was the sender! however, if
> the parameter update was caused by something else, the GUI *does* need
> to be notified.
>
> how to distinguish cheaply and easily between these two cases ?
I would not bother. Conceptually the GUI has controllers and observers
(any visual component). You may have many visual components displaying
the same parameter. e.g. in my sequencer changing a note pitch is
displayed
in the event list, the score and the piano roll. It is a lot simpler to
let
the visual state be driven by the real thing. You should of course block
an update
if you are already displaying that state.
-- Cheers Paul (P.J.Leonard)Tel: +44 (0)1225 826108 Applied Electromagnetic Research Centre, Fax: +44 (0)1225 826305 University of Bath, BATH. BA2 7AY UK
This archive was generated by hypermail 2b28 : pe maalis 10 2000 - 07:27:12 EST