On Nov 2, 2011, at 11:51 AM, Paul McNett wrote:
>> My question returns, why you don't just delay entire
>> dForm._moveRecordPointer() method instead?
>
> Because I don't want to delay the main bizobj's record pointer from moving -
> I want
> it to move immediately and update a few specific things immediately, and
> delay
> everything else.
I've been observing this thread from the sidelines, because I don't
have much of a stake in the outcome. :) But I see a framework-level distinction
that might be of use.
When you define two bizobjs to be in a parent-child relationship, the
framework will dutifully run the necessary requeries to keep them in sync. If
you don't want that to happen, then you should not be defining the relationship
that way. In Paul's case, instead of adding the child bizobjs as children of
the parent, perhaps you could create a separate collection for these delayed
requery bizobjs, and in your delay method, manually requery all members of that
collection. This way you aren't breaking the framework behavior, but still get
the behavior required for your app. IOW, this seems to be an app-specific need,
not a framework need.
Does that make any sense?
-- Ed Leafe
_______________________________________________
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]
