On 01/10/2012 02:54 PM, Simon Urbanek wrote:
On Jan 10, 2012, at 4:12 PM, Jeroen Ooms wrote:
On Tue, Jan 10, 2012 at 6:17 AM, Simon Urbanek
wrote:
Unfortunately R doesn't provide a way for this. Without changes to
unserialization (on the wishlist for a few years now, but not easy to design)
On Jan 10, 2012, at 4:12 PM, Jeroen Ooms wrote:
> On Tue, Jan 10, 2012 at 6:17 AM, Simon Urbanek
> wrote:
>> Unfortunately R doesn't provide a way for this. Without changes to
>> unserialization (on the wishlist for a few years now, but not easy to
>> design) the best you can do is to check the
On Tue, Jan 10, 2012 at 6:17 AM, Simon Urbanek
wrote:
> Unfortunately R doesn't provide a way for this. Without changes to
> unserialization (on the wishlist for a few years now, but not easy to design)
> the best you can do is to check the native symbols for NULL pointers on usage
> and then r
I don't think anyone has yet mentioned that the canonical way to save
lattice plots is to save the object produced by lattice, and print() it
again when required.
recordPlot was only ever intended to be a temporary expedient, as the
help page says.
On 10/01/2012 14:17, Simon Urbanek wrote:
On Jan 10, 2012, at 1:06 AM, Jeroen Ooms wrote:
> The underlying problem turns out to be serialization of objects of
> class "NativeSymbolInfo". When these are serialized and unserialized,
> the memory address turns into a nullpointer, causing the fail. To fix
> it, one can simply create new nati
The underlying problem turns out to be serialization of objects of
class "NativeSymbolInfo". When these are serialized and unserialized,
the memory address turns into a nullpointer, causing the fail. To fix
it, one can simply create new nativeSymbolInfo objects. E.g:
# The old example:
library(lat
