Vista not recognizing MouseLeave, MouseUp

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • rory.groves@gmail.com

    #1

    Vista not recognizing MouseLeave, MouseUp

    I have an C# .NET 2.0 application which runs fine on XP, but on Vista
    (Home Basic), the MouseUp event does not fire until i move the mouse
    over another control/button in the application. The same thing happens
    for the MouseLeave events. They do not fire until the mouse enters a
    different control.

    This would seem to be a huge problem, but i did not see much online
    about it.

    Does anyone know what could be causing this?
  • Family Tree Mike

    #2
    Re: Vista not recognizing MouseLeave, MouseUp

    Can't help without seeing your code, but these work fine for me on Vista.
    By the way, the MouseLeave should happen as you described. The MouseLeave
    event happens (in the form) when the mouse goes from the form to a control.
    I have a feeling you are not describing the action or expectation correctly.

    <rory.groves@gm ail.comwrote in message
    news:94b2d062-2f3b-44b8-9f85-68d10ec8ee3d@a2 9g2000pra.googl egroups.com...
    >I have an C# .NET 2.0 application which runs fine on XP, but on Vista
    (Home Basic), the MouseUp event does not fire until i move the mouse
    over another control/button in the application. The same thing happens
    for the MouseLeave events. They do not fire until the mouse enters a
    different control.
    >
    This would seem to be a huge problem, but i did not see much online
    about it.
    >
    Does anyone know what could be causing this?

    Comment

    • rory.groves@gmail.com

      #3
      Re: Vista not recognizing MouseLeave, MouseUp

      On Nov 15, 8:01 am, "Family Tree Mike"
      <FamilyTreeM... @ThisOldHouse.c omwrote:
      Can't help without seeing your code, but these work fine for me on Vista.
      By the way, the MouseLeave should happen as you described.  The MouseLeave
      event happens (in the form) when the mouse goes from the form to a control.
      I have a feeling you are not describing the action or expectation correctly.
      >
      The code shouldn't matter in this case, as all my controls are
      affected by this problem. I'm taking about both native and 3rd party
      controls are showing erratic behavior in Vista while there is no
      problem whatsoever in XP.

      For example, i have a MouseLeave() event in a foreground form that
      causes the form to become semi transparent when the mouse leaves the
      form bounds. This does not happen in Vista until I move the mouse into
      a second foreground form at which point the first foreground form
      proceses the MouseLeave() code.

      Its as if the MouseEnter, MouseHover, and MouseDown events fire
      normally, but MouseLeave and MouseUp do not fire until MouseEnter/
      Hover is called on a different control.

      Comment

      • Family Tree Mike

        #4
        Re: Vista not recognizing MouseLeave, MouseUp

        I made a form1 that contains the following for mouseenter and mouseleave:

        void Form1_MouseEnte r(object sender, EventArgs e)
        {
        OtherForm.Opaci ty = 0.5;
        this.Opacity = 1.0;
        }


        void Form1_MouseLeav e(object sender, EventArgs e)
        {
        this.Opacity = 0.5;
        OtherForm.Opaci ty = 1.0;
        }

        OtherForm is just an instance of another form that is shown. As I move out
        of or into form1, the opacity switches as expected. I don't need to move
        into form two to get the event propogated.

        Perhaps a key difference is that I am building and running on Vista. I used
        VS 2008 targeting .Net 2.0.


        <rory.groves@gm ail.comwrote in message
        news:9fbea36c-88b5-4d89-b265-ab54416c40fa@d4 2g2000prb.googl egroups.com...
        On Nov 15, 8:01 am, "Family Tree Mike"
        <FamilyTreeM... @ThisOldHouse.c omwrote:
        Can't help without seeing your code, but these work fine for me on Vista.
        By the way, the MouseLeave should happen as you described. The MouseLeave
        event happens (in the form) when the mouse goes from the form to a
        control.
        I have a feeling you are not describing the action or expectation
        correctly.
        >
        The code shouldn't matter in this case, as all my controls are
        affected by this problem. I'm taking about both native and 3rd party
        controls are showing erratic behavior in Vista while there is no
        problem whatsoever in XP.

        For example, i have a MouseLeave() event in a foreground form that
        causes the form to become semi transparent when the mouse leaves the
        form bounds. This does not happen in Vista until I move the mouse into
        a second foreground form at which point the first foreground form
        proceses the MouseLeave() code.

        Its as if the MouseEnter, MouseHover, and MouseDown events fire
        normally, but MouseLeave and MouseUp do not fire until MouseEnter/
        Hover is called on a different control.

        Comment

        Working...