This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 20243 - distinguishing Cancel / Prev, Next, Finish
Summary: distinguishing Cancel / Prev, Next, Finish
Status: RESOLVED WORKSFORME
Alias: None
Product: platform
Classification: Unclassified
Component: Dialogs&Wizards (show other bugs)
Version: 3.x
Hardware: PC All
: P4 blocker (vote)
Assignee: Jiri Rechtacek
URL:
Keywords:
Depends on: 20685
Blocks:
  Show dependency tree
 
Reported: 2002-02-07 08:35 UTC by David Simonek
Modified: 2008-12-23 14:30 UTC (History)
2 users (show)

See Also:
Issue Type: TASK
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description David Simonek 2002-02-07 08:35:37 UTC 
when storeSettings() is called, users can often want to distinguish between
"positive" call (Prev, Next, Finish) and "negative" (Cancel).
Why is storeSettings called upon Cancel? Should we provide some better way of
distinguishing then listening on Wizard property?
(see http://openide.netbeans.org/servlets/ReadMsg?msgId=254507&listName=dev)
Comment 1 Marek Grummich 2002-07-22 11:17:04 UTC 
Set target milestone to TBD
Comment 2 Marek Grummich 2002-07-22 11:20:14 UTC 
Set target milestone to TBD
Comment 3 mslama 2002-08-05 17:54:37 UTC 
Passing to new owner
Comment 4 Jiri Rechtacek 2002-09-16 14:43:04 UTC 
depends on issue 20685. wizard need know a exit status of the panel
(positive/negative) for determination how to process storeSettings
Comment 5 Jiri Rechtacek 2003-08-26 14:06:24 UTC 
I can in WD.P.storeSettings() ask WD.getValue() for option what was
being pressed. On base this option (Cancel, Next, Finish) determine
next processing. Issue 35266 warned of getValue() returned a bad
value, it was fixed and coverage by openide/WizardDecsTest => I close
this task as works for me.
Comment 6 Quality Engineering 2008-12-23 14:30:45 UTC 
This issue had *1 votes* before move to platform component