Opened 16 years ago
Closed 15 years ago
#2331 closed defect (fixed)
ColorEntry not working with Java Bindings.
| Reported by: | warmerdam | Owned by: | warmerdam |
|---|---|---|---|
| Priority: | normal | Milestone: | 1.7.0 |
| Component: | JavaBindings | Version: | 1.5.1 |
| Severity: | normal | Keywords: | java colorentry |
| Cc: | collinsb aaime |
Description
compile:
[javac] Compiling 39 source files to c:\build\mapserver-buildkit\gdal-1.5-br
anch\swig\java\build\classes
[javac] c:\build\mapserver-buildkit\gdal-1.5-branch\swig\java\org\gdal\gdal\
ColorEntry.java:31: delete_ColorEntry(java.awt.Color) in org.gdal.gdal.gdalJNI c
annot be applied to (long)
[javac] gdalJNI.delete_ColorEntry(swigCPtr);
[javac]
Change History (3)
comment:1 by , 16 years ago
| Status: | new → assigned |
|---|
comment:2 by , 15 years ago
In r16007, I've reverted just a bit of r14319 and managed to bring back ColorTable to life. The only thing to disable was the mapping of ColorEntry.
The regression was due to r11640 (#1578) that generalized a mapping for ColorEntry. But for JAVA, there's no use of a mapping of ColorEntry, as java.awt.Color is used instead.
comment:3 by , 15 years ago
| Milestone: | 1.5.4 → 1.7.0 |
|---|---|
| Resolution: | → fixed |
| Status: | assigned → closed |
Those fixes, as many others commited for Java bindings, are for GDAL 1.7.0
Note:
See TracTickets
for help on using tickets.
Lacking the skills to properly implement GDALColorEntry for Java I have taken the least cost step to get the rest of the Java bindings working. I have stripped the color table and color entry objects out of the Java bindings in trunk (r14319) and 1.5 branch (r14320).
A more savvy swigger can hopefully correct this in the future.