Skip to content
Prev 3534 / 63421 Next

followup to graphics bug #414

"Paul Murrell" <paul@stat.auckland.ac.nz> writes:
Hmmno.. (well maybe now in the development version.) In R-release, we have

    if (dd->dp.canClip) {
        GClip(dd);
        dd->dp.polyline(n, x, y, coords, dd);
    }
    else
        CScliplines(n, x, y, coords, dd);

and CScliplines has the problem. GClip just sets the clip boundary for
the device.
Yes. Same problem. Silly thing is that the only (simple) way to fix it
seems to be to take logs, do the clipping, take antilogs, and then
have the device function take logs once again...