Hide Forgot
Created attachment 516580 [details] patch Description of problem: The mouse double-click time is set to 0.2 seconds by default. I'm been using GUI since Windows 3.1, but I cannot click that fast unless I specifically concentrate on that, and even then I need to be lucky. When I tried LXDE with Openbox, I actually assumed that double-click on the title bar doesn't work. It is not until much later that I installed obconf and found that it's supported, but the double-click time is unrealistically low. According to Wikipedia, the default double-click time for Windows is 500ms. And even that is hard for some users! Version-Release number of selected component (if applicable): openbox-3.4.11.2-8.fc15 How reproducible: Always. Every time I install Fedora, it's one of the first things I need to change. Steps to Reproduce: 1. Login into LXDE 2. Open lxterminal 3. Try double-clicking a window titlebar 4. Run obconf and see the Mouse tab Actual results: Double-clicking fast enough to maximize the window is very hard The double click time is set to 200ms. Expected results: Double-clicking just works every time, maximizing the window without any special effort. The double click time is set to 500ms. Additional info: There are two references to doubleClickTime in the source, one in data/rc.xml and another in doc/rc-mouse-focus.xml. I believe both need to be changed to 500. The current git repository of openbox also has 200 in both places. I'm going to submit the patch upsteam.
Created attachment 516741 [details] Fixed version. Now config.c is changed as well.
Yes, please send this to upstream and I'll include the commit from upstream git.
It's upstream now, commit c885c9a676e4860a68f0bdce4b926902f6597ebb. Additionally, the patch checks that the mouse didn't move too much between the clicks, which is reasonable.
openbox-3.5.0-5.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/openbox-3.5.0-5.fc16
openbox-3.5.0-5.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/openbox-3.5.0-5.fc17
I've installed openbox-3.5.0-5.fc16 on Fedora 16, but the bug is still there! If I remove ~/.config/openbox, log out and log in, I have this in ~/.config/openbox/lxde-rc.xml: <doubleClickTime>200</doubleClickTime> I have no idea where that number comes from now. If I log in on the text console while logged out in X, ~/.config/openbox does not exist, so it's not saved by the old process. I uninstalled obconf, which still has default double click time 200, but it made no difference. It's clear that the double click time is less than 500, as only very fast double clicks have an effect. doubleClickTime in /etc/xdg/openbox/rc.xml is 500. I even created a new user, logged in with LXDE and found that the double click time is 200. So the bug is not fixed.
Package openbox-3.5.0-5.fc16: * should fix your issue, * was pushed to the Fedora 16 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing openbox-3.5.0-5.fc16' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-4975/openbox-3.5.0-5.fc16 then log in and leave karma (feedback).
That's what I did yesterday, except that I downloaded the package from the link in the comment 4.
That seems to come from /usr/share/lxde/openbox/rc.xml from the lxde-common package. I think that should be a new bug, the default config and code in openbox has 500 ms now.
(In reply to comment #9) You are right, Miroslav, it comes from that file. The name lxde-rc.xml should have been a hint for me. So I have no objections regarding the proposed update for openbox. It's so disappointing that the same setting needs to be fixed in so many places (obconf has 200 as well) :(
openbox-3.5.0-5.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.
openbox-3.5.0-5.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.