Dblclick - Buglist

Resolved bugs are not deleted, but the version that solves them is mentioned beside.

The term middle-click refers to a click of the middle mouse button during the simulator is enabled (so it will be a software double-click).

The most obvious workaround concerning these bugs is to use real double clicking. All mouse actions that are not related to the middle button are not touched, so they always work as usual.
However, once you get used to middle clicks, it is hard to switch between the methods.

To all who actually use this program, and have NT4 w. SP4 or later: it is strongly suggested to use version 2.1+. See the readme.txt for the explanation.
The serious bugs that are solved by version 2.1 are solved under NT4 SP4+ only, where the low level mouse hook is available.

Here they are, latest first (those that hurt are colored red):
(timestamp: 2006.09.20)

• 2005.02.28 - Annoying failure of functionality: (solved in v2.1)
  Notepad++ (a nice text editor) behaves like TextPad (see below). Middle-click behaves as a simple left click.
  This bug will not be solved. It seems that the mouse events reach in a strange way the edit area of NotePad++. Which window handles the messages? Or am I missing something on MDI?
  Reason: probably known. Solution: on old systems not known yet.
• 2004.12.08 - BUG: (solved in v2.1)
  The Equation Editor strikes back in v2.0: see the previous EqEditor bug...
  Middle clicking in an equation in MSWord2000 will start the Equation Editor, but it behaves incorrectly. Different symptoms may occour: the text input is not inside the equation object (and can't be forced there); the object gets into resize mode (and won't leave that). As far as I saw the equation object will remain unchanged after you click somewhere inside Word. But that's not sure...
  In general, middle clicking on embedded objects in Word will cause suffering and data loss!!!
  Reason: unknown. Solution: on old systems no idea.
• 2004.12.08 - BUG: (occours in v2.0, solved in v2.1)
  The beloved MS Word 2000... (see the previous Word bug)
  Under v2.0 the endless Maximize/Restore doesn't happen any more. But middle clicking on the title bar when NOT maximized will freeze Word. The mouse cursor doesn't change, and text input is impossible. An Alt-Tab will sometimes solve the problem, but sometimes Word is just kicked out by the operating system.
  I still have no idea, and again only Word is affected from the Office package.
  Reason: unknown. Solution: on old systems no idea.
• 2003.11.14 - BUG: (different behaviour in v2.0, solved in v2.1)
  MS Word 2000 again - serious bug. A middle-click on the title bar of Word will cause an endless loop of Maximize and Restore operations of the window. You must close Word from Task Manager (if you have such a thing), cos' you can't do anything with it.
  Thanks to Karaj for reporting this.
  I have no idea... it seems that only Word is affected from the whole Office package. But only Office2000 was tested. I wonder why Word is so different from Excel/PowerPoint in this matter?.
  Reason: unknown. Solution: on old systems no idea.
• 2003.11.07 - Annoying failure of functionality: (solved in v2.1)
  A middle-click in the TextPad editor behaves as a simple left click. The middle button must be double clicked to achieve a standard double click.
  Thanks to Karaj for reporting this.
  This bug will not be solved. Its cause is that the inner window of TextPad does not ask for double click notification from Windows. My simulated double clicks never reach it. TextPad probably deals with double clicks internally. Any program that does this is beyond my control. However some clever hack might exist...
  Reason: known. Solution: on old systems not possible.
• 2003.11.05 - Annoying failure of functionality: (probably solved in v2.1, but not tested)
  In the main window of Rational Rose there is a list with all kind of class names in it. A double click on a name should open that class. If a class name doesn't fit in the list (too long), it will appear as a tooltip when the mouse is over it. In this special "tooltip case" a middle-click has no effect.
  Thanks to Karaj for reporting this. Damn, I can't test this.
  Reason: unknown. Solution: on old systems no idea.
• 2003.11.05 - Annoying failure of functionality: (probably solved in v2.1, but not tested)
  A middle-click on the main window of Winamp 5 doesn't shrink it to that "single line" mode.
  Thanks to Karaj for reporting this.
  Winamp 2.x behaves well, but only the title bars are sensitive to this method.
  Reason: unknown. Solution: on old systems no idea.
• 2003.10.04 - BUG: (solved in v2.1)
  In Microsoft Word (2000) a middle-click on an embedded sound object will play it infinitely (until you close Word). Word may cause exception when closing (this means NO save!)
  Reason: unknown. Solution: on old systems no idea.
• 2003.10.04 - BUG: (different behaviour in v2.0, solved in v2.1)
  The Equation Editor of MSOffice (2000) may seem to freeze when starting to edit an equation through a middle-click on it in a Word document.
  Temporary solution: a few Esc keypresses and switches with Alt-Tab should get you back to the 'normal' Word. Excel had no problems...
  Reason: unknown. Solution: on old systems no idea.
• 2003.09.04: (does not appear with the low-level hook in v2.1)
  It may happen that you close the program, but the dblclick.dll file is still locked (you can't delete it). Probably the dll is still loaded into a program's address space, which is curious, since the hook doesn't exist any more.
  I can't explain this either, but it is related to the error below.
  Reason: unknown. Solution: no idea.
• 2003.09.04: (does not appear with the low-level hook in v2.1)
  In the About dialog it may happen, that you see negative numbers for the processes/threads. That is weird and I can't explain, but it happens.
  Reason: unknown. Solution: no idea.
• 2003.09.04: (does not appear with the low-level hook in v2.1)
  In the About dialog, the "number of clicks" means how many WM_?BUTTONUP messages did all of the programs received, since these are what the hook proc. "sees".
  This does not include the generated double-click messages, so the numbers would correspond to the physical clicks, IF life would be easy.
  But it's not. If the low level hook is active, then all counts well. If not, then extra left clicks may be counted.
  Reason: unknown. Solution: no idea.

  Back to the main page

  Piece of Soft