Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
SwingWorker#setProgress throws an IllegalArgumentException if the argument isn’t from 0 to 100. I thought the main purpose of the setProgress method was to update a JProgressBar (as it was in this tutorial). If that’s the case, why limit the SwingWorker‘s progress to [0, 100] when JProgressBar‘s progress is not limited?
To the extent that this question has a constructive answer, the notion of what constitutes progress is probably best known to whatever is being modeled in the background thread. Scaling limits the amount of detail that must be exposed.
At the same time,
SwingWorkeris intended to be sub-classed. Nothing precludes adding asetProgress(int progress, in min, int max)method and the attendant property change support, but it’s hard to see any advantage—the recipient would just have to scale it for display.