Uploaded image for project: 'JDK'
  1. JDK
  2. JDK-6417827

missing mouse release event

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: P3
    • Resolution: Not an Issue
    • Affects Version/s: 6
    • Fix Version/s: None
    • Component/s: client-libs
    • Labels:
    • Subcomponent:
    • CPU:
      x86
    • OS:
      windows_xp

      Description

      J2SE Version (please include all output from java -version flag):
        java version "1.6.0-beta2"
        Java(TM) SE Runtime Environment (build 1.6.0-beta2-b80)
        Java HotSpot(TM) Client VM (build 1.6.0-beta2-b80, mixed mode, sharing)

      Does this problem occur on J2SE 1.4.x or 5.0.x ? Yes / No (pick one)
       Yes

      Operating System Configuration Information (be specific):
        Windows XP Professional SP2

      Hardware Configuration Information (be specific):
        Intel Pentium III, 730 Mhz, 384 Mb RAM

      Bug Description:
      A swing application that registers to handle mouse events
      receives an inconsistent sequence when it is minimised
      and then redisplayed.
      Consistency in mouse events is that a mouse press can be
      followed by mouse drag events and IS followed by a mouse
      release. Mouse move events occur only outside
      press-drag-release sequences. Mouse drag and release occur
      only within such a sequence.

      Steps to Reproduce (be specific):

      Consider the attached program. Compile, and run it.
      Then place the pointer over its window, press the left
      mouse button and drag the mouse out of its window.
      Then, without releasing the button, hit any key.
      This has the effect of forcing the minimization of the
      window. Then releas the left mouse button, display the
      window (with ALT-TAB), and move the mouse over it.
      You will see a mouse press event that is follwed by
      a mouse move and NOT by a mouse release.
      This is disruptive for applications that perform
      operations based on mouse gestures.
      Such applications could overcome the problem by catching
      window events (posing then a constraint on the implementation
      of the enclosing window).
      The correct behaviour is to generate automatically a
      mouse release event.

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            tyao Ting-Yun Ingrid Yao (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved:
              Imported:
              Indexed: