>If it is the flicker that bothers you, would double
>buffering help ?
>
>When I find time, I'll look into this. I did not
>anticipate 200+ objects on one form.
>---Paul Barton-Davis <pbd@Op.Net> wrote:
>> [ 300 objects ]
>>
>> >That's rather a lot, isn't it?
Well, I wouldn't call it flicker. On a 486/66, a redraw of all those
objects takes measurable time, and when at least 2/3rds of them didn't
"need" a redraw (however difficult that may be to discern), it feels
very troubling.
Right now, I'm *not* using freeze/unfreeze, and I put up with a
tolerable amount of flickering (no redraw though). But its not a good
solution, partly because of the visual flicker as double redraws
occur, and partly because all that bursty X activity interferes with
the OS timer that I use (i.e. the application ends up spending much
more time inside system calls involved in X communication, and during
such periods, in general, signals cannot be delivered until the call
is complete, unless that particular call checks during its execution).
I've tried double buffering, and it requires more memory than I want
my application to require from potential users.
So any improvements in this area would be great.
--pbd
_________________________________________________
To unsubscribe, send the message "unsubscribe" to
xforms-request@bob.usuf2.usuhs.mil or see
http://bob.usuf2.usuhs.mil/mailserv/xforms.html
XForms Home Page: http://bragg.phys.uwm.edu/xforms
List Archive: http://bob.usuf2.usuhs.mil/mailserv/list-archives/