Changes between Initial Version and Version 2 of Ticket #3667


Ignore:
Timestamp:
Feb 7, 2011, 6:41:10 AM (13 years ago)
Author:
dmorissette
Comment:

Checking...

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #3667

    • Property Owner changed from sdlime to dmorissette
    • Property Status new → assigned
    • Property Component MapServer C Library → OGR Support
    • Property Severity normal → major

  • Ticket #3667 – Description

    initial v2  
    11Since MapServer 5.4.x (maybe before but 5.0.x was all right and i never tried 5.2.x) i’m facing a very annoying issue concerning DGN annotation layers : when trying to deal with text orientation, both STYLEITEM « AUTO » and manual styling using [OGR :Label…] attributes fails. Debug
    2 mode shows that LabelAngle is always read as zero while text string and color are correctly read. Worse : i tried with more recent releases of GDAL and/or MS (home made or MS4W ones) but they always crash when i’m trying to use [OGR :LabelSize] (other attributes behave fine except - still - the angle). When it happens, the debug file shows that every attributes is read as empty or zero.
    3 The last working context was GDAL 1.5.2 with MS 5.0 .3, and only the DGN format seems to be impacted (MITAB stills behaves OK). The OGR style string seems correct, and changing the parameters order (so that it looks like MITAB’s) didn’t help. The code in mapogr.cpp seems fine and except the conditional compilation settings regarding OGR Style C API which was not used in MS 5.0.x i don’t know what could cause this behaviour, except the OGR DGN driver itself (memory handling issue ?).
     2mode shows that LabelAngle is always read as zero while text string and color are correctly read.
     3
     4Worse : i tried with more recent releases of GDAL and/or MS (home made or MS4W ones) but they always crash when i’m trying to use [OGR :LabelSize] (other attributes behave fine except - still - the angle). When it happens, the debug file shows that every attributes is read as empty or zero.
     5
     6The last working context was GDAL 1.5.2 with MS 5.0.3, and only the DGN format seems to be impacted (MITAB stills behaves OK). The OGR style string seems correct, and changing the parameters order (so that it looks like MITAB’s) didn’t help.
     7
     8The code in mapogr.cpp seems fine and except the conditional compilation settings regarding OGR Style C API which was not used in MS 5.0.x i don’t know what could cause this behaviour, except the OGR DGN driver itself (memory handling issue ?).