[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug swing/24216] AbstractDocument.remove fires incorrect DocumentEvent

From: thebohemian at gmx dot net
Subject: [Bug swing/24216] AbstractDocument.remove fires incorrect DocumentEvent
Date: 9 May 2006 18:43:44 -0000

------- Comment #4 from thebohemian at gmx dot net  2006-05-09 18:43 -------
First of all: I cannot confirm the original problem. However I changed code in
various related classes in the last months and have not seen this PR before.

The problem roman describes was introduced by the integration of the
DocumenFilter. It turns out that the RI has some funny (aka unspecified)
behavior when it comes to whether remove, replace and insertString turn into
no-ops because of the values of their parameters.

Eg. replace() has no effect when (length == 0  && (text == null ||
text.length() == 0) but remove will never turn into a no-op. For insertString()
it is similar: It does nothing when (text == null || text.length() == 0).

Doing nothing means they do not call the DocumentFilter's method and probably
not the internal method (which would in a normal situation unconditionally
change the document's data).

I have a patch ready but would like to work on a comprehensive mauve text



reply via email to

[Prev in Thread] Current Thread [Next in Thread]