|
From: Ethan M. <merritt@u.washington.edu> - 2009-09-16 15:27:02
|
On Wednesday 16 September 2009, Benjamin Lindner wrote: > Ethan Merritt wrote: > > So far as I know, the EMF terminal works fine. > > The big problem we have is that some [all?] versions of Windows > > have difficulty viewing them. > > > > If I do the following change > > diff -r 0cb8214be97a term/emf.trm > --- a/term/emf.trm Wed Aug 26 16:14:37 2009 +0200 > +++ b/term/emf.trm Wed Sep 16 16:26:48 2009 +0200 > @@ -1496,7 +1496,7 @@ > } > EMF_write_long(strlen(str)); /* true number of characters */ > EMF_write_long(76); /* offset to text */ > - EMF_write_long(ETO_NO_RECT); /* ExtTextOut options */ > + EMF_write_long(0); /* ExtTextOut options */ > EMF_write_rectl(0, 0, 0, 0); /* bounding, never used */ > EMF_write_long(0); /* offset to intercharacter spacing array */ > for (i = 0; i < len; i++) > > then it suddenly *does* work for me. No idea why, though. That's a huge help (though a total mystery). How did you think of changing that write in particular? Microsoft Developer Network documentation states: ETO_NO_RECT: This bit indicates that the record does not specify a bounding rectangle for the text output. And in fact we don't provide one (see 2 lines below "never user"). |