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 91295 - Project properties panel is incompatible with other projects
Summary: Project properties panel is incompatible with other projects
Status: RESOLVED DUPLICATE of bug 77935
Alias: None
Product: cnd
Classification: Unclassified
Component: Project (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Thomas Preisler
URL:
Keywords:
: 96614 (view as bug list)
Depends on:
Blocks:
 
Reported: 2006-12-19 19:15 UTC by _ gordonp
Modified: 2007-05-25 00:46 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description _ gordonp 2006-12-19 19:15:42 UTC
Our project properties panel is modal yet has an Accept button. Other project
types are not modal and have no Accept button (which really doesn't make any
sense on a modal dialog).

We should remove the Accept button and make the panel non-modal. This will
make us compatible with other NetBeans project types.

Note: I made this P2 due to the incompatibility, not the overall seriousness
of the issue. I feel strongly we need to be as compatible as possible!
Comment 1 Thomas Preisler 2006-12-19 20:01:07 UTC
The content of our property dialogs is dynamic. The Apply button is used to
update the view based on the current set of values. For instance, if you switch
project type from Application to Static Library, the nodes in the left panel are
updated  reflecting the new project type when you click Apply. This user model
is copied from Visula Studio. So the apply button certainly has a purpose even
in modal mode.

Removing the Apply button requires the view to change/update when some of the
property values change. This model may work too. 

Changing the property dialog to be non-modal shouldn't be a big issue. In fact,
it was non-model for a long time but I changed it to modal because of some
issues. I have forgotten the details.
Comment 2 _ gordonp 2006-12-19 20:32:19 UTC
An Apply buttons has a fairly specific meaning (as defined in most UI
guidelines). I'd prefer something different so its meaning isn't confusing
to users (as it was to me).

Also, how is the user going to know the current function of the button?
Why doesn't this happen automatically when the project type is changed?
Is the project type the only field which needs this update? If so, can't
it be automated (so a change in project type triggers the apply changes
feature of the panel)? If not, consider a different button label (Update
perhaps?).
Comment 3 Thomas Preisler 2006-12-19 20:57:34 UTC
as I said, this model including the name of the button is taken straight from
Visual Studio and that's the only reason why it is as it is. This doesn't mean
we cannot change it to something better or to something that is closer to
NetBeans' model. In fact, I think we should. You are not the first suggesting
removing the Apply button and updating the view automatically based on the
currect selection. It's not only the project type that has this effect. Compiler
Selection is another. 
Comment 4 _ gordonp 2007-02-26 19:35:04 UTC
*** Issue 96614 has been marked as a duplicate of this issue. ***
Comment 5 Thomas Preisler 2007-04-13 00:40:05 UTC
will not fix in 5.5.1. downgrading to p3.
Comment 6 Thomas Preisler 2007-05-25 00:46:36 UTC

*** This issue has been marked as a duplicate of 77935 ***