Maybe it could work if you adopted the convention that the collection properties are based on the listbox object name, e.g.
Form.listbox1__currentItem Form.listbox1__selectedItems etc. You would have to adjust these properties after the first listbox, but I assume the component could manage the selection just by knowing the listbox object name. Not tested. The other way to do it is to generate the entire form including the list boxes with code. A lot more work up front, but hopefully worth it in the long run. John DeSoi, Ph.D. > On Oct 30, 2018, at 3:21 AM, Jeremy Roussak via 4D_Tech > <4d_tech@lists.4d.com> wrote: > > It seems to me that that won’t work with entity boxes unless I put them in > subforms or set up the variables (your Form.xx variables) myself. Even then, > the component can’t “know” which variables to use unless I tell it directly, > because it can’t read the box to determine what they are. > > That seems to me a retrograde step, a step back from “everything about a > listbox is readable and configurable in code” which we had reached before. ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
