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 58124 - [41cat] No 'Up-to-date' after Undo
Summary: [41cat] No 'Up-to-date' after Undo
Status: RESOLVED WONTFIX
Alias: None
Product: obsolete
Classification: Unclassified
Component: vcsgeneric (show other bugs)
Version: 4.x
Hardware: PC Windows XP
: P3 blocker with 1 vote (vote)
Assignee: issues@obsolete
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-20 23:19 UTC by ulfzibis
Modified: 2009-12-21 07:27 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 ulfzibis 2005-04-20 23:19:02 UTC
[ BUILD # : last Q-build ]
[ JDK VERSION : 1.5.0_02 ]

When changing something in a Java document VCS indicator changes to 'Locally Modified'. When undoing the change, the indicator is not changing back to 'Up-to-date'.
Comment 1 Martin Entlicher 2005-04-21 09:30:20 UTC
It always worked like this. We do not store the original copy, so we do not know
that the file happens to match the original.
This can not be P2, it's nothing serious, there's Refresh for such cases. The
timestamp of the file is different from the timestamp of the last retrieved copy
(stored in CVS/Entries), therefore the file is reported as [Locally Modified]
until you run Refresh on it.

I do not think this will ever be implemented, at least not in the near future.
Can I have guaranteed that the editor has unlimited undo and that after all
undo's the file is in the original state?

Scheduling for future, might be resolved as wontfix in the future. The
implementation is problematic, it must be carefully thought out.
Comment 2 ulfzibis 2005-04-21 23:38:47 UTC
> ... therefore the file is reported as [Locally Modified]
> until you run Refresh on it.
I agree.

> Can I have guaranteed that the editor has unlimited undo and that
> after all undo's the file is in the original state?
How you manage backtracking of *-badge ?
Comment 3 Martin Entlicher 2005-04-22 15:33:55 UTC
> How you manage backtracking of *-badge ?
That is a job of Editor, I do not do that. But the *-badge is there just till
the file is saved, therefore it's easier. It's enough to remember the number of
changes and undos since the last save. What do you request is to remember the
number of changes and undos instantly across all save operations if the file was
Up-to-date originally. This is likely possible, but it needs to be evaluated
whether a dependency on Editor would be required and whether the added value is
worth the effort, as this does not seem to be much common use-case.
Comment 4 ulfzibis 2005-04-22 19:14:19 UTC
Thanks for your comments.

As I remember wright the cvs-refresh didn't work correctly in former netbeans
versions. There the only chance for [Up-to-date] was to post a new commit to the
repository. Now the cvs-refresh feature works fine.

Perhaps for backtracking via undo remember the undo-stack position in
cvs-[Up-to-date]-state.
Comment 5 Quality Engineering 2009-12-21 07:27:52 UTC
This bug was reported against NetBeans IDE 6.0 or an older release, or against a non-maintained module. NetBeans team does not have enough resources to get to this issue, therefore we are closing the issue as a WONTFIX. If you are interested in providing a patch for this bug, please see our NetFIX guidelines for how to proceed. 

We apologize for any inconvenience.


Thank you.
The NetBeans Team