2009/7/21 nullPointer <epicfan@gmail.com>:
Just a guess: maybe it is better to persist a morph(s) as is - as original objects - just keep them somewhere in classvars. Then to create a new view of it, just do a #deepCopy.
Perhaps could be a combined solution. Persist the morph in a method, but only load one time, if class var is nothing. Then in the next times send #deepCopy to prototype morph . That could be a solution for the velocity :) I believe than EasyMorphicGUI works of that way too.
Regards.
Any reasons to stay anonymous? Hey, we don't/can't harm you in any way :) Instead, i think that it would be not only me, who could say, that we would really like to help you with that.
-- View this message in context: http://n2.nabble.com/Persist-a-morph-in-a-message.-tp3292117p3295437.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
-- Best regards, Igor Stasenko AKA sig.