On 19 February 2010 00:49, Andrea Aime wrote: >> I'm afraid that even GeoTools suffers from sub-standard coding >> sometimes. I'll give the person responsible a good talking to. > > LOL!! >
You may laugh Andrea but a few stern words seem to have done the trick. I think it's fixed now... http://jira.codehaus.org/browse/GEOT-2938 Guillaume, to get the fixed code you can do one of the following... If you use maven as your build too you can swap over to GeoTools version 2.6-SNAPSHOT. For this you will need to add the snapshot repository to your pom.xml. Please see instructions here... http://geotools.org/quickstart.html#what-is-a-geotools-snapshot-version-and-how-do-i-use-it Or you can download the jar manually from here... http://repo.opengeo.org/org/geotools/gt-swing/2.6-SNAPSHOT/ Or if you build GeoTools from source you can grab the modified source for RenderingExecutor (the class where the problem was lurking) from here... http://svn.osgeo.org/geotools/branches/2.6.x/modules/unsupported/swing/src/main/java/org/geotools/swing/RenderingExecutor.java Michael ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Geotools-gt2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
