search for: dalgard

Prompted by Peter Dalgard's recent elegant "intbin" function, I have been playing with the extension to converting reals to binary representation. The decimal part can be done like this: decbase <- function(x, n=52, base=2) { if(n) { x <- x*base paste(trunc(x), decbase(x%%1, n-1, base), sep=&q...

...pws.prserv.net/tap/posting-guide-draft2.html. (Posted there to make the HTML formatting easy to read.) I've tried to incorporate the suggestions people posted and mailed to me. Quite a few were of the form "too long, but you should add this..." :-) Brian Ripley, Jason Turner, Peter Dalgard, Patrick Burns, Frank Harrell, Gabor Grothendieck, Spencer Graves, and Patrick Connolly all made valuable suggestions that I've tried to incorporate (apologies if I omitted anyone!) Jonathan Baron gave some much appreciated suggestions on how to make it more concise, which I have probably not...

Thanks Professor Dalgard. If you have a different way to fix the bug then I'd be happy to test it. Or whatever. I understand that maybe some data was being referenced before it had been initialized. I could also support moving the R_ProcessEvents call in another place, but it seems one would also like to generate som...

...a call to R_ProcessX11Events() _after_ the GEaddDevice2(dd, devname). Option (b) is probably the easiest. > > Paul: Does this analysis look roughly right? > > -pd > > > > >> On 26 Apr 2019, at 01:23 , frederik at ofb.net wrote: >> >> Thanks Professor Dalgard. >> >> If you have a different way to fix the bug then I'd be happy to test >> it. >> >> Or whatever. I understand that maybe some data was being referenced >> before it had been initialized. I could also support moving the >> R_ProcessEvents call in an...

...all to R_ProcessX11Events() _after_ the GEaddDevice2(dd, devname). Option (b) is probably the easiest. >>> Paul: Does this analysis look roughly right? >>> -pd >>>> On 26 Apr 2019, at 01:23 , frederik at ofb.net wrote: >>>> >>>> Thanks Professor Dalgard. >>>> >>>> If you have a different way to fix the bug then I'd be happy to test >>>> it. >>>> >>>> Or whatever. I understand that maybe some data was being referenced >>>> before it had been initialized. I could also suppor...

...ack it out if the driver fails to start, or (b) add a call to R_ProcessX11Events() _after_ the GEaddDevice2(dd, devname). Option (b) is probably the easiest. Paul: Does this analysis look roughly right? -pd > On 26 Apr 2019, at 01:23 , frederik at ofb.net wrote: > > Thanks Professor Dalgard. > > If you have a different way to fix the bug then I'd be happy to test > it. > > Or whatever. I understand that maybe some data was being referenced > before it had been initialized. I could also support moving the > R_ProcessEvents call in another place, but it seems...

...art, or (b) add a call to R_ProcessX11Events() _after_ the GEaddDevice2(dd, devname). Option (b) is probably the easiest. >> Paul: Does this analysis look roughly right? >> -pd >>> On 26 Apr 2019, at 01:23 , frederik at ofb.net wrote: >>> >>> Thanks Professor Dalgard. >>> >>> If you have a different way to fix the bug then I'd be happy to test >>> it. >>> >>> Or whatever. I understand that maybe some data was being referenced >>> before it had been initialized. I could also support moving the >>&...

Consider the following example: # substitute a with b in the indicated function. Seems to work. > z <- substitute( function()a+1, list(a=quote(b)) ) > z function() b + 1 # z is an object of class call so use eval # to turn it into an object of class expression; however, # when z is evaluated, the variable a returns. > eval(z) function()a+1 Why did a suddenly reappear again

I don't recall exactly what I did 18 years ago eiher and I likely don't have the time to dig into the archives and reconstruct. I can imagine that the issue had to do with the protocol around creating and mapping windows. Presumably the segfault comes from looking for events on a window that hasn't been created yet, or has already been destroyed, leading to a NULL reference somewhere.