Bug 80830 - File navigation panes respond erratically to mouse clicks
File navigation panes respond erratically to mouse clicks
Product: Red Hat Linux
Classification: Retired
Component: gftp (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jonathan Blandford
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2002-12-31 14:01 EST by Michael Knepher
Modified: 2013-04-02 00:17 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-02-06 12:03:36 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michael Knepher 2002-12-31 14:01:17 EST
Description of problem:
File navigation panes don't respond as expected to mouse clicks. Single mouse
clicks will select items, but double-clicking will not always have desired
effect (e.g., changing directories, queueing files for upload/download).
Clicking furiously on directories sometimes seems to have no effect, and
requires either manually entering path or selecting a folder and hitting
"Enter". Clicking furiuosly many times on a file will sometimes cause the file
to be queued. After a while, the panes will begin occasionally responding to
normal double-clicks.

Version-Release number of selected component (if applicable):
gFTP 2.0.14
rpm version: gftp-2.0.14-1

How reproducible: Sporadic

Steps to Reproduce:
1. Launch gFTP
2. Attempt to navigate filesystem in local or remote panes using the mouse
3. Double-click on an entry
Actual results:
Only occasional response to double-click when trying to navigate directories.

Expected results:
Change directories on double-click, queue files for upload/download with

Additional info:
Comment 1 Jonathan Blandford 2003-02-18 17:24:52 EST
is this local or remote, or just remote.  Also, you haven't changed your double
click speed, have you?  I can't obviously duplicate this behavior.

Note You need to log in before you can comment on or make changes to this bug.