Branch: refs/heads/master
Home: https://github.com/Starlink/starjava
Commit: 9b66cdfb5d632dd70bd749ee4dcd1105c4ca75bf
https://github.com/Starlink/starjava/commit/9b66cdfb5d632dd70bd749ee4dcd1105c4ca75bf
Author: Mark Taylor <[log in to unmask]>
Date: 2014-09-11 (Thu, 11 Sep 2014)
Changed paths:
M topcat/src/docs/figures/SiaMultiWindow.gif
Log Message:
-----------
topcat: fix broken screenshot
Poorly edited multi SIA window screenshot had some pixels out of place.
Paste over them.
Commit: fde3b8513bd1c54c5e3587c9f27511425e468835
https://github.com/Starlink/starjava/commit/fde3b8513bd1c54c5e3587c9f27511425e468835
Author: Mark Taylor <[log in to unmask]>
Date: 2014-09-12 (Fri, 12 Sep 2014)
Changed paths:
M topcat/src/docs/sun253.xml
M ttools/src/main/uk/ac/starlink/ttools/convert/Conversions.java
Log Message:
-----------
topcat: stop doing auto-conversion of time columns
The Conversions class can automatically convert string columns to
numeric ones. But the newer DomainMapper machinery does the same thing.
These do not play nicely with each other, and in particular make
Time plots in topcat (but not stilts) fail for ISO-8601-formatted time
coordinates. Hack round this by turning off time conversions in
the Conversions class. This will break some things, for instance
statistics calculations and plotting in non-time plots for
ISO-8601 columns.
However, these didn't work particularly well before (the values
were just interpreted as decimal years AD), and I'm hoping they
weren't much used.
In the long term, I think the Conversions class should be phased out,
replaced by more pervasive use of DomainMappers.
But another possibility would be to specify what kind of conversion
is required when it's used (in ColumnDataComboBox).
Compare: https://github.com/Starlink/starjava/compare/4850722cacbd...fde3b8513bd1
|