Ed Leafe wrote: > On May 8, 2009, at 10:01 AM, <[email protected]> > <[email protected]> wrote: > >> IMHO... >> If we are closing the form and we have confirmed that we want to >> cancel, >> then the status of the bizobj's is a "don't care" issue. In the >> unlikely >> event that they are referenced somewhere else, then we should let >> that other >> reference "worry" about issuing the bizobj.cancel() >> >> Do you not agree? > > > No, I don't. Bizobjs can be shared between forms. And, as John > demonstrated, the cancel() takes all of 0.004 seconds. > > There is something else going on when your form is closing. I don't > have the time to dig into it right now, as I'm at work, but whatever > it is, it isn't the cancel() call.
It looks to me like it may be cancelAll(). And I think I may agree with Larry, that if another form is also using the same bizobj (is this really sane to do?) that this form shouldn't cancelAll() because that other form may not like that very much. So, is the form issuing cancelAll() on the main bizobj? If so, I think it shouldn't. But, it's hard to tell from the profiler results because it is sorted by cpu time, so I can't tell which is calling what. Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/[email protected]
