Copy field problem

Bob Sneidar bobs at twft.com
Tue Aug 31 10:43:45 CDT 2010


I think this is working exactly as intended. If you were working in an object oriented application, and you made an instance of a field object, you wouldn't want the contents of the field to ALSO be instanced. Data should by nature be separate from the form objects that display them. Hypercard confused us a bit because the card with all it's objects was both the record AND the form. A very odd thing if you think about it. But with Revolution, as I have said before, I think cards should really be used as forms, and the persistent data should be stored elsewhere. 

Try making your field a label field. I bet the content copies fine. 

Bob

 
On Aug 30, 2010, at 10:37 PM, Alex Shaw wrote:

> Hi
> 
> Having a annoying problem with copying a field from a (specific) stack.
> 
> See below for basic test stack with a single field with some content..
> http://www.harryscollar.com/teststack.rev
> 
> This unusual stack was initially created via code, stripped back of unneeded controls and saved.
> 
> When I load this stack into the IDE, create a new stack and run the following command at the message box..
> copy fld 1 of card 1 of stack "teststack" to card 1 of stack "Untitled 1"
> 
> .. I get a blank field on the new stack!
> 
> Yet when I copy and paste the field onto another new stack and try copying, it works and copies the contents too. It also works if I manually recreate a test stack with another test field.
> 
> Very strange because any new field created on "teststack.rev" will now copy over to any other stacks with empty contents.
> 
> I've checked relevant properties but nothing seems out of place.
> 
> Argh! Starting to pull out my hair over this problem.
> 
> regards
> alex
> 
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution




More information about the use-livecode mailing list