Bug 43699 - [Progress] [Properties] [Preference] Property/Preference pages should use a common operation/progress monitor
Summary: [Progress] [Properties] [Preference] Property/Preference pages should use a c...
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2003-09-25 17:04 EDT by Pratik Shah CLA
Modified: 2019-09-06 16:14 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pratik Shah CLA 2003-09-25 17:04:38 EDT
We have added several pages to the Properties dialog, and a lot of these can
potentially modify the workspace.  Unfortunately, under the current
implementation, hitting OK in the Properties dialog after changing a few
pages means that each page will launch its own ProgressMonitorDialog, do its
thing, and then build and/or validate the project.  The biggest disadvantage
is that the project is being built/validated several times, which can be a
time-consuming process.  Having several progress dialogs pop up is also a 
usability concern.

I have noticed that the Preferences dialog has the same problem.  You can do
the following to see the problem:
1)  Go to Java -> Compiler and change one of the options that would cause it
re-compile all project in the workspace.
2) Without hitting Apply or OK, go to Plug-in Development -> Compilers and
change another option there that can cause it to re-compile all projects as 
well.
Now, when you hit OK, it will try to re-compile all the projects twice.

So, as a solution to this problem, I propose that the Property/Preferene 
dialogs use a WorkspaceModifyComposedOperation when invoking performOk() on all 
pages and pass an IProgressMonitor, that can be shared by all the methods, as a 
parameter to that method.
Comment 1 Nick Edgar CLA 2006-03-15 14:07:16 EST
Reassigning bugs in component areas that are changing ownership.
Comment 2 Tod Creasey CLA 2007-06-14 08:17:20 EDT
There are currently no plans to work on this although we would be happy to review patches.
Comment 3 Susan McCourt CLA 2009-07-09 19:30:05 EDT
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:14:01 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.