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 25175 - CVS, PVCS: Can't see new basic variable.
Summary: CVS, PVCS: Can't see new basic variable.
Status: CLOSED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: vcsgeneric (show other bugs)
Version: 3.x
Hardware: PC Windows ME/2000
: P2 blocker (vote)
Assignee: Martin Entlicher
URL:
Keywords: UI
Depends on:
Blocks:
 
Reported: 2002-06-26 11:24 UTC by Jiri Kovalsky
Modified: 2003-07-01 13:03 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jiri Kovalsky 2002-06-26 11:24:56 UTC
Development build #200206260100 of NetBeans 3.4
Windows 2000 with JDK 1.4.1 RC build #15

Description:
============
This is quite interesting bug. Users can't create
basic variables to CVS or PVCS filesystems or at
least they are not visible in the customizer. The
most strange is that it seems like VSS was not
affected. Looks like regression ?

Steps to reproduce:
===================
1. Invoke "Versioning|Mount Version
Control|Generic VCS".
2. Select CVS profile and push "Next >" button.
3. Click "Edit Variables..." and right click
"Basic" node.
4. Choose "Add Variable", type "Name" and click "OK".
5. Push "Finish" and invoke the customizer after
the filesystem is mounted into explorer.
6. There is no "Name:" textfield in it.
Comment 1 Martin Entlicher 2002-06-26 12:06:02 UTC
This is because CONFIG_INPUT_DESCRIPTOR variable is defined. This
variable defines a descriptor of input components, that are located in
Profile panel. If this is defined, basic variables have no meaning
then.

This should be solved as a UI problem. The functionality is O.K., but
from the UI it's not apparent, that the basic variables do not play
the former role.
Comment 2 Martin Entlicher 2002-06-26 17:52:38 UTC
Filip, do you have any idea how can we fix this?
It's necessary to let the user know, that the Basic variables have no
effect to the Profile tab when CONFIG_INPUT_DESCRIPTOR variable is
defined. But the variables can still be used by commands.

One solution, that just came to my mind:
- if the user defines CONFIG_INPUT_DESCRIPTOR variable (or if it's
already defined in the XML profile), remove all variables from the
"Basic" folder and put them all into "Accessory" folder. This will
indicate, that they have no special meaning now. The "Basic" folder
can be disabled then, so that the user can not create additional
"basic" variable, but only accessory one. The "Basic" folder can also
get a tooltip describing the reason why it is disabled.

- I will still remember, which variables are "basic" and therefore if
the user remove the CONFIG_INPUT_DESCRIPTOR variable, we'll enable the
"Basic" folder again and move all basic variables there.

Comments/suggestions?

Comment 3 Filip Rachunek 2002-06-27 11:07:21 UTC
I agree with this suggestion. Since the implications of this bug would
be confusing for users, it must be fixed and the easiest solution
seems to be the one Martin wrote.
So, let's do this (if CONFIG_INPUT_DESCRIPTOR variable is defined):

1) Move all Basic variables to Accessory node.
2) Disable Basic node and put a tooltip describing this situation on it.

And, of course, mention this case in documentation.
Comment 4 Martin Entlicher 2002-06-27 12:38:52 UTC
Thanks Filip for your comments.
I've started to implement it, but as I know there's no easy way how to
make the node "disabled".
So if it's O.K., to get the "disabled" state, I'll replace the node's
icon with gray icon, make the text gray and remove all actions and
change the tooltip. I'm not sure yet whether I'll be able to make the
tooltip gray as well.
Comment 5 Filip Rachunek 2002-06-27 13:04:31 UTC
I think that making the node non-expandable with grey icon and text
would be sufficient. The tooltip can stay "normal", there is no need
to make it grey as well.
Comment 6 Martin Entlicher 2002-06-28 11:46:27 UTC
Fixed as proposed in dev build Jun 29.
Comment 7 Jiri Kovalsky 2002-08-05 11:11:02 UTC
Sorry, but it's not perfect yet. If CONFIG_INPUT_DESCRIPTOR variable
is empty, Basic becomes editable and takes over all necessary
variables, however proper settings are not visible on Profile tab of
the wizard. Trying to verify in development build #200208050100 of
NetBeans 4.0.

Steps to reproduce:
===================
1. Invoke "Versioning|Mount Version Control|Generic VCS".
2. Select CVS profile and push "Next >" button.
3. Click "Edit Variables..." and expand "Accessory" node.
4. Delete value of CONFIG_INPUT_DESCRIPTOR variable.
5. Push "OK" and "< Back" buttons. No setting is visible.
Comment 8 Martin Entlicher 2002-08-06 10:14:41 UTC
Starting to work on a fix...
Comment 10 Jiri Kovalsky 2002-11-07 18:56:47 UTC
Verified in development build #200211070100 of NetBeans 4.0.
Comment 11 Jaroslav Tulach 2002-12-03 09:55:20 UTC
Hi. This issue is marked as 3.4.1_CANDIDATE. It means that it should be
integrated into release341 one branch. The plan at
http://www.netbeans.org/devhome/docs/releases/34/index.html expected beta1 to be
produced on Dec01. That did not happen due to a lot of outstanding not
integrated candidates like this one. 

Would it be possible to spend few minutes by backporting this fix? Thank you in
advance.
Comment 12 Martin Entlicher 2002-12-05 14:01:31 UTC
Merged into release341 branch.
/cvs/vcsgeneric/src/org/netbeans/modules/vcs/advanced/VcsCustomizer.java,v 
<--  VcsCustomizer.java
new revision: 1.87.6.1.4.1; previous revision: 1.87.6.1
Comment 13 Quality Engineering 2003-07-01 13:03:28 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.