Results 1 to 3 of 3

Thread: Why should any swing call back implementation execute quickly?

  1. Jan 20th, 2011, 01:08 AM #1
    ydeveloper66
    ydeveloper66 is offline Junior Member
    Join Date
    Jan 2011
    Posts
    4

    Default Why should any swing call back implementation execute quickly?

    Hi all,

    I have a java swing query as above. can you please answer me?
    Last edited by ydeveloper66; Jan 20th, 2011 at 01:13 AM.
    java ecommerce
    Reply With Quote Reply With Quote
  2. Feb 21st, 2011, 07:27 AM #2
    Lucitywaskey
    Lucitywaskey is offline Junior Member
    Join Date
    Feb 2011
    Posts
    1

    Default

    Yes I come back...
    Hydroxycut
    Reply With Quote Reply With Quote
  3. Mar 9th, 2011, 05:54 PM #3
    adamarmistead
    adamarmistead is offline Senior Member
    Join Date
    Mar 2009
    Location
    Oregon
    Posts
    116

    Default

    If by "swing callback implementation" you mean a chunk of code executing on the Event Dispatch Thread. Then the answer is, so it won't block the user interface, as Swing is single threaded. While the EDT runs your long running process it is not responding to user interaction, this makes your application appear sluggish, or in worst case scenarios, freeze completely until the long running process is finished.

    If you mean something run off of the EDT then there is no reason it needs to be a short process.
    Reply With Quote Reply With Quote
« Previous Thread | Next Thread »

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

Forum Rules