On Feb 22, 2019, at 8:43 AM, Kirk Brooks wrote:
> 2) if you need DIALOG just wrap it in another object. I like to use 'data'.
> So you can do this:
>
> $obj:=New object("data";$oChildObject)
>
> DIALOG("myForm";$obj)
>
> It's simple to change the references on the form objects to
>
Drew,
On Thu, Feb 21, 2019 at 10:27 AM Drew Waddell via 4D_Tech <
4d_tech@lists.4d.com> wrote:
> I am unable to do $oChildObject:=null in my actual situation because I am
> passing that object into a Dialog
You run into this when passing the object to a new form using DIALOG. I use
two
ech-boun...@lists.4d.com> On Behalf Of Drew Waddell via
4D_Tech
Sent: Thursday, February 21, 2019 1:28 PM
To: Olivier Deschanels ; 4D iNug Technical
<4d_tech@lists.4d.com>
Cc: Drew Waddell
Subject: RE: Object notation bug?
I am unable to do $oChildObject:=null in my actual situation
having loop over
all properties in the child and remove them individually?
Drew
-Original Message-
From: Olivier Deschanels
Sent: Thursday, February 21, 2019 1:21 PM
To: 4D iNug Technical <4d_tech@lists.4d.com>
Cc: Drew Waddell
Subject: Re: Object notation bug?
Hi,
Hi,
That’s not a bug. That’s normal.
$oChildObject:=New object create a reference to a object store in $oChildObject
OB SET($oParentObject;"ChildInformation";New object) push another reference
into the $oParentObject but the old reference still exist because $oChildObject
isn’t cleared.
you
I am trying to figure out if this is a bug or not. This is a watered down
version of something I am trying to do:
C_OBJECT($oParentObject;$oChildObject)
$oChildObject:=New object
$oParentObject:=New object
6 matches
Mail list logo
