Hi Julie... I like Dante's suggestion of using the auto-save concept to solve the problem; will this approach fold into the rest of the application well? In my experience, I've discovered that "auto-save" works best when its used consistently throughout the entire application rather than as an isolated surprise.
One approach I try to use when thinking about situtations like this is, "Am I trying to do too much in this view?" I sense that there are two competing purposes to this one view (Print vs. Edit) and you might be better served by using another pattern. The master-detail arrangement might help: The details of a check are edited within a dedicated child dialog or panel that can be reached from the view you've proposed. The Save and Cancel buttons are moved to the child view, leaving Print and Close in the parent view along side the list of checks. This approach should be less ambiguous - no shifting labels or confusing buttons. Good luck, and let us know how it turns out. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=40834 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... disc...@ixda.org Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
