JDK-6481521 : Double click interval settings from DE not honored on Linux
  • Type: Bug
  • Component: client-libs
  • Sub-Component: java.awt
  • Affected Version: 6
  • Priority: P5
  • Status: Closed
  • Resolution: Duplicate
  • OS: linux
  • CPU: x86
  • Submitted: 2006-10-12
  • Updated: 2011-01-19
  • Resolved: 2006-10-13
Related Reports
Duplicate :  
Relates :  
Description
FULL PRODUCT VERSION :
java version "1.6.0-rc"
Java(TM) SE Runtime Environment (build 1.6.0-rc-b100)
Java HotSpot(TM) Client VM (build 1.6.0-rc-b100, mixed mode, sharing)


ADDITIONAL OS VERSION INFORMATION :
Linux fly 2.6.15-27-386 #1 PREEMPT Sat Sep 16 01:51:59 UTC 2006 i686 GNU/Linux

A DESCRIPTION OF THE PROBLEM :
As far as I know Java on Linux reads multi click interval from .Xresource/.Xdefault (depends on distribution) file. If file isn't present some default value (200ms on my system) is used.

On Gnome user can change double click interval using gnome-mouse-properties or via GConf *but* this value isn't writed to .Xresource/.Xdefault. This way interval used by Java is different from system one and, since it usually much smaller (Gnome default is 400ms) it is quite problematic to end user.

While debugging I've found that desktop setting is readed and stored in 'gnome.Net/DoubleClickTime' key in XToolkit desktop properties - so this value should be used instead default 200 ms (stored under 'awt.awt.multiClickInterval' key).

Two issues:
- what if .XResource/.Xdefault is present and contains multiClickTime property of value different that Gnome setting. Persoanlly I think that Gnome should take precedence
- why Gnome (KDE too, I've heard) doesn't save interval to .Xresource file. It would be good to contact Gnome devs and discuss this issue

I think that fixing this bug should have high priority - default 200ms is sometimes too small even for me (person with 10+ years experience with various desktop environment), not experienced or physically challenged users will have serious problems with performing doubleclick.


REPRODUCIBILITY :
This bug can be reproduced always.

Comments
EVALUATION There is an issue about mouse smudge area described in 5039416 and others that is very similiar to this one. Here we face with the same problem as with smudge settings: we should either have a single settting for Java applications on all the supported platforms or have different settings for each platform separately according to the native behaviour. Both of the approaches have their advantages and disadvantages, so I'm not sure if this bug should be fixed or not.
13-10-2006