"Herfried K. Wagner [MVP]" <hirf-spam-me-here@gmx.at> wrote in message
news:%231yezH4uDHA.536@tk2msftngp13.phx.gbl...
> * "Hamilton Woods" <HamiltonWoods@accutrol.com> scripsit:
> > Where do we go from here?
>
> Let's wait if somebody tells us if it works in .NET 1.1.
>
> --
> Herfried K. Wagner [MVP]
> <http://www.mvps.org/dotnet>

> Is there a reason that the MouseUp event for a windows form TreeView control
> fires when the mouse is moved while the left mouse button is held down?
> I think you'll find this one repeatable. Make a scratch windows form
> project. Place a TreeView control on the form. Add some nodes to the
> control. Add an event handler for its MouseUp event. Set a breakpoint in
> that event handler. Watch what happens. I'm using VS.NET 1.0.
> If you have an empty TreeView control, the MouseUp event fires when the left
> mouse button is pressed, even before the mouse is moved. Huh.

"Herfried K. Wagner [MVP]" <hirf-spam-me-here@gmx.at> wrote in message
news:OdVMt22uDHA.3416@tk2msftngp13.phx.gbl...
> * "Hamilton Woods" <HamiltonWoods@accutrol.com> scripsit:
> > Is there a reason that the MouseUp event for a windows form TreeView
control
> > fires when the mouse is moved while the left mouse button is held down?
> > I think you'll find this one repeatable. Make a scratch windows form
> > project. Place a TreeView control on the form. Add some nodes to the
> > control. Add an event handler for its MouseUp event. Set a breakpoint
in
> > that event handler. Watch what happens. I'm using VS.NET 1.0.
> > If you have an empty TreeView control, the MouseUp event fires when the
left
> > mouse button is pressed, even before the mouse is moved. Huh.
>
> I am able to repro the behavior you describe on a .NET 1.0 machine. I
> would consider that to be a bug.
>
> --
> Herfried K. Wagner [MVP]
> <http://www.mvps.org/dotnet>

> Where do we go from here?

"Tim Wilson [MVP]" <Tim_Wilson@[DieSpamDie]Rogers.com> wrote in message
news:O0QJGM4uDHA.3116@tk2msftngp13.phx.gbl...
> It seems to work fine in 1.1
>
> --
> Tim Wilson
> .Net Compact Framework MVP
>
> "Herfried K. Wagner [MVP]" <hirf-spam-me-here@gmx.at> wrote in message
> news:%231yezH4uDHA.536@tk2msftngp13.phx.gbl...
> > * "Hamilton Woods" <HamiltonWoods@accutrol.com> scripsit:
> > > Where do we go from here?
> >
> > Let's wait if somebody tells us if it works in .NET 1.1.
> >
> > --
> > Herfried K. Wagner [MVP]
> > <http://www.mvps.org/dotnet>
>
>

"Eric Newton" <eric@cc.ensoft-software.com> wrote in message
news:uiZZ$KZvDHA.2248@TK2MSFTNGP09.phx.gbl...
> Exactly how do you define "seems to work fine"... as in, A) it correctly
> does NOT fire MouseUp or B) MouseUp is still firing but you feel that its
> the intended behavior?
>
> --
> Eric Newton
> C#/ASP Application Developer
> http://ensoft-software.com/
> eric@cc.ensoft-software.com [remove the first "CC."]
>
> "Tim Wilson [MVP]" <Tim_Wilson@[DieSpamDie]Rogers.com> wrote in message
> news:O0QJGM4uDHA.3116@tk2msftngp13.phx.gbl...
> > It seems to work fine in 1.1
> >
> > --
> > Tim Wilson
> > .Net Compact Framework MVP
> >
> > "Herfried K. Wagner [MVP]" <hirf-spam-me-here@gmx.at> wrote in message
> > news:%231yezH4uDHA.536@tk2msftngp13.phx.gbl...
> > > * "Hamilton Woods" <HamiltonWoods@accutrol.com> scripsit:
> > > > Where do we go from here?
> > >
> > > Let's wait if somebody tells us if it works in .NET 1.1.
> > >
> > > --
> > > Herfried K. Wagner [MVP]
> > > <http://www.mvps.org/dotnet>
> >
> >
>
>