[prev in list] [next in list] [prev in thread] [next in thread] 

List:       gimp-print-devel
Subject:    Re: [Gimp-print-devel] Another question about the options system
From:       "Alastair M. Robinson" <blackfive () fakenhamweb ! co ! uk>
Date:       2004-11-09 20:41:56
Message-ID: 41912B94.8040908 () fakenhamweb ! co ! uk
[Download RAW message or body]

Hi,

Robert L Krawitz wrote:

> (it's basically one loop, and comparing what's returned against saved
> state).  I'm sure it seems more elegant to signal changes, but I'm not
> at all convinced that it's actually any simpler for application
> writers, and it's certainly not simpler for the library.

It wasn't simplicity or even elegance that was bothering me, it was the 
potential for performance problems.  It turns out that this concern was 
unwarranted.

I now have Combos, Toggles and Sliders implemented (i.e. nearly 
everything that PhotoPrint needs for its stp_vars UI), all running 
within a self-contained notebook, and on my PIII-500 laptop I get a 
pause of no more than a quarter of a second when selecting 
Quality->Manual Control - mostly taken in drawing the three 
newly-available tabs.

This is without any caching - at the moment I'm just blindly updating 
the combo contents, toggle state, and slider bounds + current value for 
every parameter.

Given this, I no longer consider the flag I suggested necessary, at 
least unless future versions end up with three or four times as many 
parameters to handle!

All the best,
--
Alastair M. Robinson


-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
_______________________________________________
Gimp-print-devel mailing list
Gimp-print-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/gimp-print-devel
[prev in list] [next in list] [prev in thread] [next in thread]