[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: handle graphics

From: Ole Jacob Hagen
Subject: Re: handle graphics
Date: Sun, 17 Jul 2005 21:39:10 +0000
User-agent: Mozilla Thunderbird 1.0 (X11/20041206)


I believe that Octave should not be aware of "handle graphics"-properties, since handle graphics should be handled by each visualisation application/plugin. Octave should provide a "handle-graphics"-layer, that should be used by each visualisation application.

As you know, Oplot and Props is implemented in this way.
Octave (as m-script) checks if data is of correct type, and sends the data to Oplot. Communication layer of Oplot receives these data, and set the respective Props-data. Since visualisation classes in Oplot inherites the property-callbacks from Props, the callbacks are executed. Each visualisation classes handles each of this callbacks separately.

Another point.
If Octave is aware of handle graphics object, wouldn't this result in multiple duplications of same data, both in Octave, and visualisation application? This should be avoided. Or do people want handle graphics to be implemented as references to datasets?
An example:
v = randn(1,100);
h = plot(v)
would then result in one instance of v, and h-g implementation in Octave gives a reference/pointer to v? In visualisation application the same data would exist both in application and graphics card?

If I implement the behaviour found in CMO into Props, Oplot could send back to Octave, and not only as replies, since a event-loop on Octave side is required.


Ole J.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]