> On Apr 30, 2020, at 4:43 PM, lists via 4D_Tech <[email protected]> wrote: > > OK, based on this design, we are back to using variables (or dynamic > variables) for data entry of anything that needs any kind of processing done > to it after an entry, having to load the values to these data entry objects > when loading the form, and copying the values back when we want to save any > user changes. > > OR > > We can use the Form.XXX notation to gain the advantage of that new nifty > option, but lose the generic coding ability. > > I'd say it's a choice, but the lack of the ability to address an object from > within generically definitely seems to be a glaring omission...
If there is such an issue trying to get object values to work right, what’s the reason to use them at all? I know everyone is all excited about object notation, but it’s not mandatory. Why should we even consider using it if doesn’t do what we need? I’m sure there are some areas where it’s useful, but it sounds like there’s a lot where it isn’t. Am I missing something? Randy Kaempen Intellex Corporation ********************************************************************** 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] **********************************************************************
