You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@harmony.apache.org by "Alexey A. Ivanov (JIRA)" <ji...@apache.org> on 2006/12/12 14:40:22 UTC
[jira] Updated: (HARMONY-2645) [classlib][swing]
j.s.undo.UndoManager ignores the limit set with setLimit() method
[ http://issues.apache.org/jira/browse/HARMONY-2645?page=all ]
Alexey A. Ivanov updated HARMONY-2645:
--------------------------------------
Attachment: HTest2645.java
The application which demonstrates the difference.
--- Harmony output ---
true
------
--- RI output ---
false
javax.swing.undo.CannotUndoException
at javax.swing.undo.UndoManager.undo(UndoManager.java:273)
at HTest2645.main(HTest2645.java:14)
------
The RI behavior is correct.
The second addEdit() in the application should cause the previous UndoableEdit be removed from the list of edits (and die() should be called on it).
> [classlib][swing] j.s.undo.UndoManager ignores the limit set with setLimit() method
> -----------------------------------------------------------------------------------
>
> Key: HARMONY-2645
> URL: http://issues.apache.org/jira/browse/HARMONY-2645
> Project: Harmony
> Issue Type: Bug
> Components: Classlib
> Reporter: Alexey A. Ivanov
> Attachments: HTest2645.java
>
>
> Calling setLimit(1) does not affect the number of edits stored in UndoManager.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira