Problem solved. Martin Morgan pointed out to me that the error occurs
because in the method in raster I used, to get the function name which
I need for branching, the naive approach:
funname <- as.character(sys.call(sys.parent())[[1]])
from the code of callGeneric Martin deduced that I should ins
On 13-02-13 6:43 PM, Henrik Bengtsson wrote:
Just an observation/FYI on the new DESCRIPTION field 'VignetteBuilder'
available in R devel:
Unlike other package fields (Depends, Imports and Suggests),
VignetteBuilder does not support version specifiers, e.g.
VignetteBuilder: R.rsp (>= 0.8.2)
Ye
I get an error when using self-defined (not standard) functions with mapply
with S4 objects from the raster package that I develop: "Error in
as.character(sys.call(sys.parent())[[1]]) : cannot coerce type 'closure'
to vector of type 'character'". Does anyone understand why? The problem is
illust
Just an observation/FYI on the new DESCRIPTION field 'VignetteBuilder'
available in R devel:
Unlike other package fields (Depends, Imports and Suggests),
VignetteBuilder does not support version specifiers, e.g.
VignetteBuilder: R.rsp (>= 0.8.2)
but only
VignetteBuilder: R.rsp
If adding a vers
I would like to see the default for stringsAsFactors set to FALSE. As for
posting descriptions of all the horrors, also post descriptions of the
ensuing increases in productivity that many will see as they no longer have
to go back and fix code that is not working because they forgot to add
as.is=T
On 13/02/2013 8:40 AM, Charles Geyer wrote:
Please do not change the defaults for the show.signif.stars option or for
the default.stringsAsFactors option. Backward compatibility is more
important than your convenience. The same sort of argument could be made
for changing the default of the "["
Dear John and Milan,
thanks a lot for your input. Unfortunately, this is by far not the only
think preventing my dialog from working, I am afraid. This was the start
of the matter, as far as I remember, but I think that buttons like my
refresh button etc. will also need special attention - as
Dear Milan and Ulrike,
The purpose of errorCondition() is to put a dialog in the state it was in prior
to the erroneous input, reflecting, e.g., prior selections. Like all Rcmdr
utility functions, its use isn't mandatory -- it's simply meant to be
convenient and to encourage some consistency in
Please do not change the defaults for the show.signif.stars option or for
the default.stringsAsFactors option. Backward compatibility is more
important than your convenience. The same sort of argument could be made
for changing the default of the "[" function from drop = TRUE to drop =
FALSE. It
On 13-02-13 8:30 AM, Milan Bouchet-Valat wrote:
Le mercredi 13 février 2013 à 12:33 +, Michael Dewey a écrit :
At 18:01 11/02/2013, Ista Zahn wrote:
FWIW my view is that for data cleaning and organizing factors just get
it the way. For modeling I like them because they make it easier to
und
Le mercredi 13 février 2013 à 12:33 +, Michael Dewey a écrit :
> At 18:01 11/02/2013, Ista Zahn wrote:
> >FWIW my view is that for data cleaning and organizing factors just get
> >it the way. For modeling I like them because they make it easier to
> >understand what is happening. For example I
On 13-02-13 7:33 AM, Michael Dewey wrote:
At 18:01 11/02/2013, Ista Zahn wrote:
FWIW my view is that for data cleaning and organizing factors just get
it the way. For modeling I like them because they make it easier to
understand what is happening. For example I can look at the levels()
to see w
Le mercredi 13 février 2013 à 13:16 +0100, Ulrike Grömping a écrit :
> Milan,
>
> I am not closing the dialog, but without the dialog in the search space,
> I cannot properly refer to it any more using e.g. the Rcmdr function
> errorCondition.
> It has been a long time ago that I wrote this; I d
On 13-02-13 7:25 AM, peter dalgaard wrote:
On Feb 12, 2013, at 20:19 , Duncan Murdoch wrote:
I think you are misreading what Peter wrote. He wasn't defending
that point of view, he was describing it.
Yes. However, that being said, there is the point that the whole
thing has been designed t
On Wed, Feb 13, 2013 at 7:33 AM, Michael Dewey wrote:
> At 18:01 11/02/2013, Ista Zahn wrote:
>>
>> FWIW my view is that for data cleaning and organizing factors just get
>> it the way. For modeling I like them because they make it easier to
>> understand what is happening. For example I can look
At 18:01 11/02/2013, Ista Zahn wrote:
FWIW my view is that for data cleaning and organizing factors just get
it the way. For modeling I like them because they make it easier to
understand what is happening. For example I can look at the levels()
to see what the reference group will be. With chara
On Feb 12, 2013, at 20:19 , Duncan Murdoch wrote:
> I think you are misreading what Peter wrote. He wasn't defending that point
> of view, he was describing it.
>
Yes. However, that being said, there is the point that the whole thing has been
designed to work within the paradigm that I descr
Milan,
I am not closing the dialog, but without the dialog in the search space,
I cannot properly refer to it any more using e.g. the Rcmdr function
errorCondition.
It has been a long time ago that I wrote this; I don't have a small
reproducible example right now. Below is an example of what I
Le mardi 12 février 2013 à 14:45 +0100, Ulrike Grömping a écrit :
> Dear DevelopeRs,
>
> I've been struggling with the new regulations regarding modifications to
> the search path, regarding my Rcmdr plugin package RcmdrPlugin.DoE. John
> Fox made Rcmdr comply with the new policy by removing the
19 matches
Mail list logo
