Re: color_radio_property implementation

[Przemek Klosowski]

   I didn't say it's impossible, but inefficient because of the
   continuous conversion
   from Octave/C++ to java (mainly converting octave_value objects into Java
   equivalent). For instance when doing 3D rotation with the mouse of a complex
   surface, this will significantly impacts the performances.

Tcl had the same problem, and dealt with it by caching the converted
values: IIRC the value was accessed in the form in which it was
get/set, and it was converted only if it was get/set through the
_other_ interface. This of course was done transparently in the
API. There are little problems with this approach, e.g.  when you're
dealing with 0.1 vs. its binary value--- you get 'shimmering' noise in
LSB depending how you last accessed the value.