Re: ProgressMonitorInputStream test

Andrew Thompson wrote:


...


A search of the bug DB on ProgressMonitorInputStream
shows the following hits:

<http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4075058>
Mentioned as an example in support of interruptible streams.

<http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4140706>
One string in a list data object, not otherwise used.

<http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4209604>
Seems to have been used inside the EDT.
Solution - don't block the EDT. 'Closed, will not be fixed'.

<http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6456237>
"Remove synchronized keyword from method declarations in Swing"
PMIS is listed as one of the classes that uses it. I cannot
see how removing the synchronized keyword would fix this,
but I might be wrong.

<http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=5089193>
"JTextArea.setText() wastes megabytes of memory!"
Uh-huh. This is a little more informative in that it gets
the underlying ProgressMonitor* and adjusts the params.
I don't know how I missed the getProgressMonitor()
method! (Except of course, the obvious answer that I
am a moron who does not take enough care to RTFM.)
Will check this out further.
(though the actual bug report does not relate to PMIS,
and is closed as a duplicate).

* This has answered one of my questions, namely..


2.5 seconds is the default. (2 secs. pass before it even
considers appearing, then, if the read is expected to take
less than half a second, it will not pop up).

These questions are still open..


..continuing the investigation.

--
Andrew Thompson
http://www.athompson.info/andrew/

Message posted via http://www.javakb.com