Object get type has been changed in 16r something. Probably when collections were introduced in r4 but I wasn’t paying attention.
The change is it no longer returns the ‘Object Array’ type (39). Any value that begins with a [ is interpreted as ‘Is collection’ (42). Object arrays still work just fine but any code that evaluates an object by key type needs to be updated. Object arrays can still be declared and used, as in list boxes, but 4D’s object methods relate to things beginning with [ as a collection. This cleans up a couple of issues. First is the indexing issue. 4D arrays begin numbering at 1. The 0 element is perfectly usable in nearly all cases but OBJECT SET ARRAY and Object get array drop it when manipulating arrays. Collections start at 0 like pretty much everything else and are consistent. Next, collections are much more robust and capable of handling mixed values for each element whereas in an object array each element can only be an object. -- Kirk Brooks San Francisco, CA ======================= *We go vote - they go home* ********************************************************************** 4D Internet Users Group (4D iNUG) FAQ: http://lists.4d.com/faqnug.html Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
