Drew,
On Thu, Feb 21, 2019 at 10:27 AM Drew Waddell via 4D_Tech <
[email protected]> 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 approaches when i need to do this:
1) put the form into a subform on the parent form. You can hide it until
needed. Make the subform object an object and you're all set. This way you
avoid needing DIALOG.
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
Form.data.whatever. I find it more robust not the least of which because it
allows you to have a null object without crashing your form.
--
Kirk Brooks
San Francisco, CA
=======================
What can be said, can be said clearly,
and what you can’t say, you should shut up about
*Wittgenstein and the Computer *
**********************************************************************
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]
**********************************************************************
