Opened 19 years ago
Closed 9 years ago
#702 closed defect (fixed)
bug in writing data to MIF/MID
Reported by: | Owned by: | warmerdam | |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | OGR_SF | Version: | unspecified |
Severity: | major | Keywords: | |
Cc: |
Description (last modified by )
Hi, Frank, hi, Daniel In #684 we discussed about writing StyleStrings to MIF files. We were agree that StyleStrings lost. I have developed a patch for resolving that problem. I implement it only for TABPoint, TABMultiPoint, TABPolyline, TABRegion. But I am not sure that it is very good. Can be there more "laconic" decision? In this patch I have added debug strings ( printf("in TAB***") ). So, if we are writing to MIF point geometries, we must reseive "in TABPoint" message if point is TABPoint (i.e. symbol in MapInfo 3.0 notation); "in TABFontPoint" message if point is font symbol. But I found that if we are writing font symbol, we receive "in TABPoint" message. Why? Sergey Karin
Attachments (1)
Change History (2)
by , 19 years ago
Attachment: | diff-write.diff added |
---|
comment:1 by , 9 years ago
Description: | modified (diff) |
---|---|
Resolution: | → fixed |
Status: | new → closed |
It seems there's support in MIF/MID now to write styling. So closing assuming this patch is no longer needed
Note:
See TracTickets
for help on using tickets.
patch for writing data to MIF/MID