The EMF+ example found a bug in the previously untested (because unseen) EmfPlusDrawDriverString record handling.
That goes somewhere way down on the todo list.
However the EMF demo when run on my linux test system through reademf had problems with both EXTSELECTCLIPRGN records:
U_EMR_EXTSELECTCLIPRGN record: 205 type:75 offset: 4668 rsize: 16 crc32:A3D88BDC
WARNING: Corrupt record. Emitting fields above the problem.
record corruption HERE
U_EMR_EXTSELECTCLIPRGN record: 220 type:75 offset: 5216 rsize: 16 crc32:A3D88BDC
WARNING: Corrupt record. Emitting fields above the problem.
record corruption HERE
Now I need to find out why. That type of record has been tested, but it was added fairly recently, so perhaps this example explores some code path which needs work.
The EMF+ example found a bug in the previously untested (because unseen) EmfPlusDrawDriv erString record handling.
That goes somewhere way down on the todo list.
However the EMF demo when run on my linux test system through reademf had problems with both EXTSELECTCLIPRGN records:
U_EMR_EXTSELECT CLIPRGN record: 205 type:75 offset: 4668 rsize: 16 crc32:A3D88BDC
WARNING: Corrupt record. Emitting fields above the problem.
record corruption HERE
U_EMR_EXTSELECT CLIPRGN record: 220 type:75 offset: 5216 rsize: 16 crc32:A3D88BDC
WARNING: Corrupt record. Emitting fields above the problem.
record corruption HERE
Now I need to find out why. That type of record has been tested, but it was added fairly recently, so perhaps this example explores some code path which needs work.