Hi Chris,
You might want to take a look at the Task class from Swing Application
Framework. It is a great abstraction for long-running operations in
general. It's basically a fancy SwingWorker, with support for a nice
publish/process-protocol, which I think you could use for your "drip-
feed" mechanism.
Not really sure it fits your needs, but I think it's worth looking into.
Best regards,
--
Harald K
On 25. sep.. 2008, at 22.34, [EMAIL PROTECTED] wrote:
I'm starting think my problem is knowing what solution applies to my
situation. There are plenty of solutions for handling long-running
tasks in Swing. (SwingWorker, etc.) There are solutions for double
buffering for animations (BufferStrategy). But, I don't think either
of those apply to long-running rendering tasks.
Maybe a solution to that would be to drip-feed little subtasks onto
the event queue such that there is only one rendering task on the
queue at a time and user events will be interleaved in the queue
between rendering tasks.
Any other ideas or examples for maintaining a responsive UI in the
presence of long-running rendering tasks?
Thanks,
-chris
[Message sent by forum member 'cbare' (cbare)]
http://forums.java.net/jive/thread.jspa?messageID=301678
=
=
=
=
=
======================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in
the body
of the message "signoff JAVA2D-INTEREST". For general help, send
email to
[EMAIL PROTECTED] and include in the body of the message "help".
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JAVA2D-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
