On Wednesday 16 April 2008 04:14:40 pm Paul McNett wrote: > Ed, > > Can you remind me of the reason why biz.delete() must happen immediately > instead of waiting for biz.save(). And why biz.cancel() couldn't cancel > the pending deletions? > > Here's my use-case: > > Biz hierarchy, simplified: > > orders > openings > subopenings > panels > rails > stiles > > User opens the screen to modify a shutter opening. The opening has 2 > subopenings. The user removes one of the subopenings > (subopenings.delete()). The user then presses 'cancel' on the dialog. > The user opens the screen again and there's only one subopening and > associated panels. > > If this isn't something that we could put into Dabo, do you have > suggestions on how to implement this for my specific case? > > It still seems inconsistent that the other functions that modify the > dataset (new() and setFieldVal()) will cache the changes until save(), > while delete() must happen immediately without waiting for save(). > > Prior discussions I could find on this issue: > > http://leafe.com/archives/showFullThd/338986 > http://leafe.com/archives/showFullThd/189048 > > Paul How would the grid work with deletes? If the user deletes a line item it should disappear from the grid right. But if it still cached in the dataset it will be displayed - right? What should happen in the display grid?
-- John Fabiani _______________________________________________ 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]
