Kepler

Mouselisteners are used for many things in reporting, and they're causing some problems. There are times when we don't hear the change we're actually after-- e.g. there are currently ways for the user to make changes to text in the layout that will never make it into the report instance -- e.g. start typing some text in a report item, move your mouse up to the execute button, type some more, then click execute. The text you typed after moving your mouse away from that item won't be in your report instance. Also many things occur far more often than is necessary, e.g. if you simply move your pointer over a report item many methods are invoked repeatedly, some changing the model. This is wasteful and makes it hard to differentiate actual changes to the report layout.