On Thu, 24 Jan 2008, Michael Braun wrote:
> NO
>
> Hi. I'm not sure if this is an R-help or R-devel problem, so I'm
Definitely R-devel.
> starting here in the hope that someone can help (and willing to go to
> the other list if it's more appropriate). I think I am following all of
> the instru
On Thu, 24 Jan 2008, Johannes Graumann wrote:
> Prof Brian Ripley stats.ox.ac.uk> writes:
>
>>
>> On Thu, 24 Jan 2008, Johannes Graumann wrote:
>>
>>> Hello,
>>> I came across this by using R cmd check - otherwise I would probably not
>>> have
>>> noticed.
>>> One of my functions does something
NO
Hi. I'm not sure if this is an R-help or R-devel problem, so I'm
starting here in the hope that someone can help (and willing to go to
the other list if it's more appropriate). I think I am following all of
the instructions in the various manuals, but clearly I am missing something.
I hav
Kurt Hornik wu-wien.ac.at> writes:
>
> > Johannes Graumann writes:
>
> > Hi,
> > Is there any way to trick R CMD check into not throwing this error after I
> > created a dedicated "plot" incarnation for my custom function?
>
> > * checking S3 generic/method consistency ... WARNING
> > plot
Prof Brian Ripley stats.ox.ac.uk> writes:
>
> On Thu, 24 Jan 2008, Johannes Graumann wrote:
>
> > Hello,
> > I came across this by using R cmd check - otherwise I would probably not
> > have
> > noticed.
> > One of my functions does something like this:
> > # postscript()
> > # plot(1, xlim =
> Johannes Graumann writes:
> Hi,
> Is there any way to trick R CMD check into not throwing this error after I
> created a dedicated "plot" incarnation for my custom function?
> * checking S3 generic/method consistency ... WARNING
> plot:
> function(x, ...)
> plot.MQUSpecMatch:
> function
I think you just need to include the '...' as an argument to your function.
Jeff
Sent via BlackBerry from T-Mobile
-Original Message-
From: Johannes Graumann <[EMAIL PROTECTED]>
Date: Thu, 24 Jan 2008 22:03:10
To:[EMAIL PROTECTED]
Subject: [Rd] Plot definition for custom class
Hi,
Is
On Thu, 24 Jan 2008, Johannes Graumann wrote:
> Hello,
> I came across this by using R cmd check - otherwise I would probably not have
> noticed.
> One of my functions does something like this:
> # postscript()
> # plot(1, xlim = c(0, 10), ylim = c(0, 4), type = "n", ann = FALSE, axes =
> FALSE)
Hi,
Is there any way to trick R CMD check into not throwing this error after I
created a dedicated "plot" incarnation for my custom function?
* checking S3 generic/method consistency ... WARNING
plot:
function(x, ...)
plot.MQUSpecMatch:
function(x, mozlabel, labelcex)
Thanks again, Joh
Hello,
I came across this by using R cmd check - otherwise I would probably not have
noticed.
One of my functions does something like this:
# postscript()
# plot(1, xlim = c(0, 10), ylim = c(0, 4), type = "n", ann = FALSE, axes =
FALSE)
# text(1:10, 2, c("a","b"), cex = seqcex, family="mono",font=
Hi
hadley wickham wrote:
>> The problem (see also
>> https://stat.ethz.ch/pipermail/r-help/2008-January/151655.html) is that
>> cellGrobs (children of frame grobs) use their 'vp' component to store
>> the viewport that positions them within the parent frame. This means
>> that the viewport is pu
Thank you, Ben!
I've added your suggestion to R-devel.
Martin
__
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
Sorry, once again I was totally confused.
Paul
Duncan Murdoch wrote:
> On 1/24/2008 10:00 AM, Paul Gilbert wrote:
>
>> I find the error message
>>
>> >Error in MyPackage::MyFunction :
>>
>> is a bit misleading. Could it be changed to
>>
>> Error in Package::Function
>
>
> I believe
On 1/24/2008 10:00 AM, Paul Gilbert wrote:
> I find the error message
>
> >Error in MyPackage::MyFunction :
>
> is a bit misleading. Could it be changed to
>
> Error in Package::Function
I believe "MyPackage" was either the actual name of the package, or what
Johannes substituted fo
I find the error message
>Error in MyPackage::MyFunction :
is a bit misleading. Could it be changed to
Error in Package::Function
perhaps with a hint: "Possibly Package is not exporting a NAMESPACE."
(At least, I think this does not work unless Package has a namespace.)
Paul Gilbert
Hi Joh --
I guess you have something like
f <- function() {}
MyPackage::f()
If you replace that with
f <- function() {}
.onLoad <- function(libname, pkgname) {
MyPackage::f()
}
I think you'll be fine. The problem is, as the message says, at the
time of evaluation with your current scheme
On Wednesday 23 January 2008 18:24:15 Duncan Murdoch wrote:
> On 1/23/2008 11:31 AM, Johannes Graumann wrote:
> > On Wednesday 23 January 2008 17:25:38 Duncan Murdoch wrote:
> >> On 1/23/2008 11:11 AM, Johannes Graumann wrote:
> >> > ... sorry for reposting this in a more appropriate forum than
> >
On Wednesday 23 January 2008 17:25:38 Duncan Murdoch wrote:
> On 1/23/2008 11:11 AM, Johannes Graumann wrote:
> > ... sorry for reposting this in a more appropriate forum than r.general
> > ...
> >
> > Hello,
> >
> > I just don't get this and would appreciate if someone could write a line
> > or tw
18 matches
Mail list logo