harmony-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexey A. Ivanov (JIRA)" <j...@apache.org>
Subject [jira] Updated: (HARMONY-2645) [classlib][swing] j.s.undo.UndoManager ignores the limit set with setLimit() method
Date Tue, 12 Dec 2006 13:40:22 GMT
     [ 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 ---

--- RI output ---
	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


View raw message