search for: do_identifi

I found it useful to have contour be able to do line widths ... hope that the guts haven't changed an enormous amount in the current development version ... the patches are relatively trivial, mostly going by analogy with lty and col (although in my ignorance it took me a while to figure out what UNPROTECT(2) was and why it should be changed to UNPROTECT(3) ... hope this is useful. Ben

I think I am misunderstanding something about the identify() function. if we have an example such as this: > x_1:10 > y_1:10 > plot(x,y) > identify(x,y, n=1) [1] 2 3 > I clicked on two points and identify() returned both of them (2 and 3). The manual says n is the maximum number of points to be identified. If I specify n=1, should identify() return a single value?

A follow-up to PR#660 (15 Sep 2000) from Brian Ripley: > R 1.1.1 on Windows, but I think this is widespread. > > Using either > > par(cex=0.5) > plot(1:10) > identify(1:10) > > or > > plot(1:10) > identify(1:10, cex=0.5) > > ignores the cex setting. The root cause is that par(cex=0.5) > alters cexbase for the device but sets cex=1.0, and the

--=-=-= Included below are: 1) Diffs to to remove HDF5 from R 2) Diffs to pass thru --with-* options to a module's configure script during "R INSTALL". (To reiterate a plea for this capability...) This applies only to Unix, the Windows (mingw32 in my case) build approach of passing in make variables like *-CFLAGS and *-LDFLAGS works fine. The only hitch