off the top of *my* head I understand the fix is not limited to object notation.
it was an optimisation made for wakanda server that somehow got lost on its way to 4D object fields. so it's a fix at the database level. > 2018/06/14 11:54、Cannon Smith via 4D_Tech <4d_tech@lists.4d.com> のメール： > > I haven’t had time to try this myself today, but do you know off the top of > your head if this is only fixed when using dot notation? Or is it fixed when > for the old style of code as well (when we had to traverse the object tree to > the children, getting a reference to the child and then changing the child > object without changing the parent object)? ********************************************************************** 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:4d_tech-unsubscr...@lists.4d.com **********************************************************************
