[email protected] wrote: > Starting at line 157(approx)... > > if changedBizList: > queryMessage = > self.getConfirmChangesQueryMessage(changedBizList) > response = dabo.ui.areYouSure(queryMessage, parent=self) > if response == None: ## cancel > # Don't let the form close, or requery happen > return False > elif response == True: ## yes > for biz in changedBizList: > self.save(dataSource=biz.DataSource) > elif response == False: ## no > #LAL - Why to we need this? > pass > #for biz in changedBizList: > #if biz.RowCount: > #self.cancel(dataSource=biz.DataSource)
Larry, instead of sending the changed block of code, it is *much easier* if you could send a diff instead. Just start out with a clean dForm.py, make your changes, and issue: svn diff dForm.py > p Then open file 'p', select all, copy, and paste into your email message. But looking at the above, I see that it likely *is* cancel() that starts the cycle, so I think I agree with Ed that this is how it should be. However, you should be able to trap form.onClose and then just release the bizobjs there, avoiding this issue entirely. 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]
