Hi
Just to clarify, I think this IS a problem with grid.path() as well as
polypath().
For the example you give, grid.path() diverts to drawing a polygon
(because there is no 'id' specified), and the NAs in 'x' generate two
separate polygons, which get drawn one on top of the other.
The cor
On 03/08/2016 4:12 PM, Paul Johnson wrote:
I have a script that goes wrong because I assumed that seq.int would
return integers.
"int" means "internal", not "integer". Sometimes you should read the
documentation.
Duncan Murdoch
Below please see it does not unless user is super cautious a
> On Aug 3, 2016, at 3:12 PM, Paul Johnson wrote:
>
> I have a script that goes wrong because I assumed that seq.int would
> return integers.
>
> Below please see it does not unless user is super cautious about
> inserting "L" with inputs. I think seq.int should do coercion for me
> before retu
I have a script that goes wrong because I assumed that seq.int would
return integers.
Below please see it does not unless user is super cautious about
inserting "L" with inputs. I think seq.int should do coercion for me
before returning the sequence.
> xx <- seq.int(1,10)
> class(xx)
[1] "integer
Thanks luke,
>From your explanation, it seems that the signal SIGUSR1 was only triggered
when user want to break/cancel R execution, so we can't control the time
when SIGUSR1 sent. So for this defect, the best way is to make sure in the
signal handler function, we need to make sure there is no dir
