Displaying 7 results from an estimated 7 matches for "xdrawlines".
Did you mean:
xdrawline
2000 Feb 11
1
followup to graphics bug #414
...ything if any of
the coordinates was outside the allowed range (would one have to add a
per-driver piece of information giving the min and max vals?).
I wrote a prototype of some clipping code in R that I could translate to C
and stick into src/unix/devX11.c right before every call to XDrawLine or
XDrawLines. Before I go to that trouble, though: is there a better way to
do this? Is there already clipping code lying around somewhere else in R?
Is there a way to do this generically (perhaps by adding an outer clipping
region to every device at its device-coordinate limits) that would
centralize the c...
2007 Jun 08
1
Location of xgraphics routines
Hi
I have an application that uses the Xwindows graphics library. Things
like
XOpenDisplay
XDrawLine
XCreateSimpleWindow
XDrawString
and many more
Under all the CENTOS 4.X systems these were automatically loaded.
I dont have these loaded under my CENTOS 5 system.
I get a heap of undefined references when I compile the code.
Could someone tell me, point me, where these routines now reside on
1999 Feb 16
3
graphics bug: type="l" (PR#120)
The following commands illustrate a problem with graphing relatively large
data sets using the "line" option to plot:
temp <- runif(200000) # or whatever other numbers you like;
# same thing happens with a sine wave
plot(1:200000, temp) # everything fine
plot(1:200000, temp, type="l") # data gets cut off
The number of points isn't crucial. The cutoff point
1999 Feb 16
1
Missing tick marks bug on alpha solved
On some systems (alpha), tick marks don't appear on plots. The easiest
way to see the problem is something like:
> plot(0:1,axes=FALSE)
> axis(1,1:2)
The problem is in X11_Line(...) from .../src/unix/devX11.c, which is
so short I've included the whole function below:
static void X11_Line(double x1, double y1, double x2, double y2,
int coords, DevDesc *dd)
{
1998 Oct 28
1
Request for help with compiling R on a DEC Alpha
...ld:
Unresolved:
XLoadQueryFont
XOpenDisplay
XInternAtom
XCreateFontCursor
XCreateGC
XCreateWindow
XDefaultRootWindow
XSetWMProtocols
XAllocColor
XAllocNamedColor
XChangeProperty
XCheckTypedEvent
XClearWindow
XCloseDisplay
XDefaultDepth
XDefaultScreen
XDefineCursor
XDestroyWindow
XDrawArc
XDrawLine
XDrawLines
XDrawRectangle
XFillArc
XFillPolygon
XFillRectangle
XFreeColors
XFreeCursor
XFreeGC
XMapWindow
XNextEvent
XPending
XSelectInput
XSetClipRectangles
XSetDashes
XSetFont
XSetLineAttributes
XSetState
XSetWindowBackground
XSync
XTextWidth
XUnloadFont
XFindContext
XSaveContext
XrmUniqueQuark
XCreateSimpl...
2000 Feb 07
0
graphics bugs: steep slopes and large values beyond ylim (PR#414)
Some of my students have uncovered some apparent graphics bugs in
R. I think they may manifest slightly different on different platforms/
with different display devices (they sometimes report a Windows graph
that looks OK but odd results on printing).
I'm able to replicate similar problems on my Linux (RH 6.0) system.
1. abline() plots nothing, or a wrong line, when the slope is too
2000 Oct 23
3
behaviour of plot(...,type="l")
plot(rnorm(100000),type="l")
plots only about 7e4 lines while the same without type="l" works fine.
Is this a feature or a bug or is this configurable?
R : Copyright 2000, The R Development Core Team
Version 1.1.1 (August 15, 2000)
SunOS 5.5.1 Generic_103640-29 sun4u sparc SUNW,Ultra-1
Thanks
Adrian
--
Adrian Trapletti, Olsen & Associates Ltd., See-
feldstrasse