Miyako, Thanks. So if I’m writing entirely generic code to set up listboxes of any type, I need separate starting-point templates for entity selection boxes and collection boxes, just as I have separate templates for selection boxes and array-based boxes?
Jeremy > On 8 Jul 2019, at 10:17, Keisuke Miyako via 4D_Tech <[email protected]> > wrote: > > my understanding is that when you assign an entity selection (which is an > object, not collection) > as the data source of a listbox, > a kind of proxy collection is created to bind the entity selection to the UI. > > basic features are common ("This" is an object and This.property is a value), > but there are major differences between an entity and a regular object > (member methods, etc) > so not all code can be agnostic, especially if you do more than display data. > >> 2019/07/08 18:01、Jeremy Roussak via 4D_Tech <[email protected]>のメール: >> >> Apologies if this is a silly question; I’m still trying to get to grips with >> ORDA. >> >> As I understand it, an entity selection is an object. If I define a listbox >> whose source is “collection or entity selection”, must it be one or the >> other? In other words, can I change it at runtime from displaying a >> collection to displaying an entity selection? > > > > > ********************************************************************** > 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] > ********************************************************************** ********************************************************************** 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] **********************************************************************
