Thanks Eric and Jacque. I entered QCC report 14639. I altered my code to do as you suggest Eric.
I wonder how this affects how an array variable is stored in a custom property? As I understand it, the variable is automatically array encoded if you do something like "set the cArray of me to tArray" and decoded when you get it back out of the cProp. Personally I only use cProps for stuff that doesn't need to survive across runs of LC so wouldn't be affected by any changes in that area but others may not be so lucky. On Thu Feb 19 2015 at 1:18:58 PM J. Landman Gay <jac...@hyperactivesw.com> wrote: > On 2/19/2015 2:49 PM, Peter Haworth wrote: > > The > > dictionary indicates that if the new parameter, version, is not present > > then arrays are encoded the old way. None of my calls include the new > > parameter so not sure how they ended up being inaccessible in pre7 > versions. > > From what you've seen, it sounds like the default in 7.0 is to encode > the new way, and the dictionary is misleading. Richard G. mentioned on > the list that the default was the new encoding. We should clear that up, > it's going to affect me too eventually. > > -- > Jacqueline Landman Gay | jac...@hyperactivesw.com > HyperActive Software | http://www.hyperactivesw.com > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
