DynamicVariables aren't really dynamic, in the sense that they're not connected to the executing environment. In particular, their #value:during: behaviour is * store old value * run block * restore old value
which means that if you do something tricky during the block - perhaps like serialising the current context - when you deserialise the block you _don't_ have the value of the dynamic variable as it was during serialising. That might or might not affect what you're seeing though. I hadn't spoken up earlier because I'm not sure what exactly goes on during exporting/importing Zinc. frank On 10 August 2012 11:16, Mariano Martinez Peck <[email protected]> wrote: > anyone? > > > On Wed, Aug 8, 2012 at 2:45 PM, Mariano Martinez Peck > <[email protected]> wrote: >> >> Guys...we are having a strange problem when exporting/importing Zinc. We >> have a problem when executing: >> >> executeRequestResponse >> self logRequest. >> ZnSignalProgress enabled >> ...... >> >> The first time, #enable answers something wrong. The second time it is >> called, it seems to answer the correct value. >> ZnSignalProgress is a subclass of DynamicVariable.... so I guess there is >> a black magic around this. >> There is a hook in Fuel where I can substitute an object being serialized >> for something else. Should I substitute DynamicVariables with something when >> serialized? send #value before serialize it? nil something? >> >> Thanks in advance, >> >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > > > -- > Mariano > http://marianopeck.wordpress.com >
