it is not a bug. the 1st generation of form design in 4D was to bind process variables to objects and use variables directly in code. the 2nd generation of form design (v12) was to keep the bound variable empty and use pointers to reference dynamic variables.
the main difference was in the scope of the variables: process or form. I think the resulting heavy usage of pointers is rather consequential. it is bonus that pointers work in both cases, but I don't think that it should be the main focus. "Form" based design is a total rethink of how to use variables in forms. Form is an object, and an object is a reference, which drastically reduces the need for pointers. historically a pointer can only point to tables, fields, variables and arrays. it could have been extended to support object properties and collection members but that would send the wrong message. if you use Form and This, you should never want to use pointers. you should think of using object notation consistently in code and form. this is not to say that "generic" code is discouraged in ORDA. you just think of how to be generic in a different way. it feels counter intuitive coming from classic 4D code, but hard-coding object property paths everywhere is the key to writing generic and reusable code. ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
