[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Copying an object
- Subject: Re: Copying an object
- From: davidf(at)dfanning.com (David Fanning)
- Date: Tue, 31 Aug 1999 16:22:10 -0600
- Newsgroups: comp.lang.idl-pvwave
- Organization: Fanning Software Consulting
- References: <37CB9D07.A381E318@gsiukltd.freeserve.co.uk> <firstname.lastname@example.org>
- Xref: news.doit.wisc.edu comp.lang.idl-pvwave:16400
Mark Hadfield (email@example.com) writes:
> The best way I have found is to SAVE it then RESTORE it. My routine
> MGH_OBJ_CLONE provides a convenient way to do this.
> It sounds kludgy but it works surprisingly well. I have used it widely &
> successfully in my OG code for a year now. Just make sure the IDLgrModel in
> question is not a child of any other IDLgrModel or IDLgrView at the time you
> clone it.
How do you get around the problem, Mark, of restoring
an object and calling methods on it without first
compiling the object method code? Or does your
program design shield you from this problem?
David Fanning, Ph.D.
Fanning Software Consulting
Phone: 970-221-0438 E-Mail: firstname.lastname@example.org
Coyote's Guide to IDL Programming: http://www.dfanning.com/
Toll-Free IDL Book Orders: 1-888-461-0155