| Class and Description |
|---|
| com.isti.util.gui.SynchJList
Having thread-synchronization blocks on Swing objects is
not recommended because if a thread holds the object's lock and then
calls a Swing method that requires the AWT-tree-lock a deadlock can
occur if the AWT event-dispatch thread holds the AWT-tree-lock and
requires the object's lock (for repaint, etc). See 'SortedValuesJList'
for an example of how this should be done.
|
| Method and Description |
|---|
| com.isti.util.IstiEpoch.getIntEpoch()
This only supports up to the year 2038, use
IstiEpoch.getIntEpochSeconds(). |
| com.isti.util.IstiNotifyThread.sleep(long)
Use 'waitForNotify()' instead.
|
| com.isti.util.FileDownloader.terminate()
Should use the
terminateThread method instead. |
| Constructor and Description |
|---|
| com.isti.util.BooleanCp(boolean)
It is rarely appropriate to use this constructor. The static
factory
BooleanCp.valueOf(boolean) is generally a better choice,
as it is likely to yield significantly better space and time
performance. Also consider using the final fields BooleanCp.TRUE
and BooleanCp.FALSE if possible. |
| com.isti.util.BooleanCp(Boolean)
It is rarely appropriate to use this constructor. The static
factory
BooleanCp.valueOf(Boolean) is generally a better choice,
as it is likely to yield significantly better space and time
performance. Also consider using the final fields BooleanCp.TRUE
and BooleanCp.FALSE if possible. |
| com.isti.util.BooleanCp(String)
It is rarely appropriate to use this constructor. The static
factory
BooleanCp.valueOf(String) is generally a better choice,
as it is likely to yield significantly better space and time
performance. Also consider using the final fields BooleanCp.TRUE
and BooleanCp.FALSE if possible. |
| com.isti.util.gui.TimeFilteredDocument(TimeJTextField, int)
maxNumChars is not used
|