Only in a general way. My vague plan is to use sys_queuegui() to update scalars; since arrays are parts of scalars now, that would mean that any array value changes would trigger a later callback to do the graphical updating. However, unlike other GUI objects, arrays can be too large to update atomically, so something is needed to update a portion of an array and reschedule the rest. The situation gets complicated if a scalar has several arrays, or if an array's elements have their own arrays, etc.
Most likely for 0.39 I'll put sys_queuegui calls around scalars (and the IEM GUIs while I'm at it) but not attempt to do the finer-grained thing.
cheers Miller
On Fri, Aug 05, 2005 at 08:57:58PM +0200, Tim Blechmann wrote:
hi miller,
In general, the question of scheduling graphics updates is hard, especially now that (arrays can contain (lists that contain (arrays of scalars))), etc. Having "garrays" separate from the "real" data structure mechanism was always a temporary measure, and now I'm glad it's gone. But what this means is that now we need a more general way of updating changes to data. If I can think of a good one I'll get it into 0.39 (it's prety high on the dolist at the moment...)
before i'm starting to work on an implementation on my own ... have you been thinking about this?
t
-- mailto:TimBlechmann@gmx.de ICQ: 96771783 http://www.mokabar.tk
latest mp3: kMW.mp3 http://mattin.org/mp3.html
latest cd: Goh Lee Kwang & Tim Blechmann: Drone http://www.geocities.com/gohleekwangtimblechmannduo/
After one look at this planet any visitor from outer space would say "I want to see the manager." William S. Burroughs