-
I can't reproduce this with the current release (22.84.16). It sounds like a duplicate of bug 1184087 which has been fixed in 22.84.10:
* Render an empty character instead of terminating with failed assertion
if T1lib doesn't return a usable glyph (e.g. at very small \magnification factors.
2009-09-10 19:05:08 UTC in xdvik
-
Thanks a lot for the report and patch; fixed in CVS (rev. 1.173 of util.c).
2009-09-02 23:01:05 UTC in xdvik
-
stefanulrich committed patchset 3403 of module xdvik to the xdvik CVS repository, changing 2 files.
2009-09-02 22:59:12 UTC in xdvik
-
stefanulrich committed patchset 3402 of module xdvik to the xdvik CVS repository, changing 1 files.
2009-09-02 22:50:45 UTC in xdvik
-
stefanulrich committed patchset 3401 of module xdvik to the xdvik CVS repository, changing 1 files.
2009-08-24 09:47:16 UTC in xdvik
-
good :-) Closing as "Invalid/not a bug" since XDrawRectangle ought to work - but I guess I'll replace it by XDrawLines in future releases just to be on the safe side.
2009-08-23 19:36:52 UTC in xdvik
-
That's really weird - it must mean that XDrawRectangle is somehow broken in your X implementation ... searching the web for bug reports didn't turn up anything though. Does using the following work?
XPoint points[5];
points[0] = ll;
points[1] = ul;
points[2] = ur;
points[3] = lr;
points[4] = ll;
XDrawLines(DISP, mane.win, globals.gc.high, points, 5, CoordModeOrigin);
/*.
2009-08-23 16:07:13 UTC in xdvik
-
really strange. The next line would be the XDrawRectangle command. Maybe there's something wrong with that function? Could you try the following code in dvi-draw.c:
XPoint points[2];
points[0] = ul;
points[1] = ll;
fprintf(stderr, "drawing at: %d, %d, %d, %d\n",
min_x, min_y, max_x, max_y);
XDrawLines(DISP, mane.win, globals.gc.fore, points, 2, CoordModeOrigin);
/*...
2009-08-23 11:44:18 UTC in xdvik
-
And if you run xdvi with
-sync -debug dvi
does the "drawing at: ...." occur after the SETCHAR... commands?
Another thing to try: in read_events in texk/xdvik/events.c, replace:
for (;;) {
globals.ev.ctr = event_freq;
by:
for (;;) {
sleep(1);
globals.ev.ctr = event_freq;
recompile, and run this on your minimal example file - this will make drawing really slow, and...
2009-08-23 09:21:25 UTC in xdvik
-
At this point it's probably best to add more debugging code; I've attached a diff for texk/xdvik/dvi-draw.c, could you please apply it with:
cd texk/xdvik
patch < diffs
then recompile, do another forward search for your minimal DVI file and send me the output? It should print something for every redraw/expose event.
2009-08-21 19:05:42 UTC in xdvik
