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 23388 - VCS Groups node does not fire PropertyChange event
Summary: VCS Groups node does not fire PropertyChange event
Status: CLOSED WONTFIX
Alias: None
Product: obsolete
Classification: Unclassified
Component: vcscore (show other bugs)
Version: -FFJ-
Hardware: PC Linux
: P4 blocker (vote)
Assignee: Milos Kleint
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-05-13 09:44 UTC by David Kaspar
Modified: 2003-07-01 12:55 UTC (History)
0 users

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 David Kaspar 2002-05-13 09:44:24 UTC
How to reproduce:
1) Open VCS Groups window
2) Open Properties of VCS Groups node
3) Open Properties of VCS Groups node once again
4) Change value of some property in the first
Properties window
5) See second Properties window
6) ERROR - Property is not changed too.
7) NOTE - The same problem is with VCS Group nodes
Comment 1 Milos Kleint 2002-05-14 10:12:05 UTC
fixed in trunk.. i figured same probs apply to some properties of
javacvs filesystem.. fixed that as well..
Comment 2 Jiri Kovalsky 2002-06-10 15:10:58 UTC
Are you sure Milos you commited the fix ? It seems like nothing
changed if I reproduce the procedure. Reopening ...
Development build #200206100100 of NetBeans 3.4.
Comment 3 Milos Kleint 2002-07-09 13:52:57 UTC
it was fixed for individual groups nad the javacvs filesystem. for the
main group node, the fix is complicated and not worth the efford since
the value doesn't get lost, and there's only a visual difference in
the property sheets. And I can't think of a real-life workflow when
you use the following scenario in a meaningful way.
Comment 4 Jiri Kovalsky 2002-07-09 15:41:22 UTC
Okay. No objections from me. Any comments Davide ?
Comment 5 Quality Engineering 2003-07-01 12:55:52 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.