Re: [ jEdit-users ] Comments on 4.0pre4

[Slava P. <sl...@je...>]

On Sat, 2002-01-26 at 13:35, John Gellene wrote:
> Here are a few comments on the new release, running under Windows 2000 SP1
> and Sun JDK 1.4RC1:
> 
> (1) Plugin Manager:  The progress bar window is captioned "Removing plugins"
> when plugins are being downloaded.

Fixed.

> (2) QuickNotepad:  the jar needs the latest version of QuickNotepad.props
> from CVS, otherwise the old dependency on EditBus prevents the plugin from
> loading.

The copy in the my tree (and hence the CVS) does not have an EditBus
dependency.

> (3) Firewall:  there is an error message saying that the plugin is obsolete,
> but it it is included in the installation package.

[slava@emu slava]$ jar tf jedit40pre4install.jar |grep Firwall
[slava@emu slava]$ 

> (4) Text Area drawing:  Selecting a block caret still causes the text area
> below the caret to be drawn in incorrect, unreadable colors.  I've been
> fretting about this since JDK1.4 was first released in beta, but now I think
> I finally found the problem.  There appears to be a bug in Graphics2D (at
> least in the Windows peer classes) that prevent the paint mode from being
> reset when a call to setPaintMode() is made after a call to setXORMode().
> Perhaps it's a race condition. This bug was mentioned on the newsgroups in
> connection with JDK 1.1 and appears to have resurfaced. The solution is to
> clone the graphics object by a call to Graphics.create() and have the block
> caret drawn by the cloned object. With that approach, I see no degradation
> in performance or signs of significant leakage in native resources, and the
> text renders correctly. A patch is attached.  Now I can post a 4.0
> screenshot without embarrassment!

Thanks, applied.

> (5) The pre-JDK1.4, Windows-only version of the WheelMouse plugin should be
> modified so that it will not complete loading and displays an error message
> in a 1.4 VM.  The application cannot exit normally when it is present with
> the 1.4 JDK, so properties and plugin settings cannot be saved.  That is too
> much mischief to left unchecked.

Maybe the old plugin should be removed altogether? Since it's Windows
only and uses native code.
-- 
Slava Pestov