[haiku-appserver] Re: progress and status

  • From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
  • To: haiku-appserver@xxxxxxxxxxxxx
  • Date: Wed, 18 May 2005 16:07:11 +0200 CEST

Adi Oanca <adioanca@xxxxxxxxxxxxxx> wrote:
> Axel D=F6rfler wrote:
> > Stefano Ceccherini <burton666@xxxxxxxxxxx> wrote:
> > > I think BeBook is wrong here. Just try the test app 
> > > (GetMouseTest) I 
> > > committed in src/tests/kits/interface.
> > > It eats up all the mousemoved messages.
> > I think you're wrong here: that you don't get those messages should 
> > be 
> > an implementation detail: you're calling GetMouse() until a 
> > MouseUp() 
> > event would be triggered - ie. you're eating all events by 
> > yourself.
>       Have other questions.
>       What if I move the mouse outside the window and release the mouse 
> button=3F
>       Why steal B=5FMOUSE=5FMOVED messages destined for other views in this 
> window=3F

That's how it works. If you're using GetMouse() outside of MouseDown() 
you might be using it the wrong way.

>       Why do you find this GetMouse(..., true) so useful=3F I simply hate 
> this method!
> I really think we should use the standard, *nicer* way: Mouse*();

Using GetMouse() is the old standard that we have to support. No matter 
if we like it or not; IIRC no one said it's oh so useful - we just have 
to have it working correctly as advertised.


Other related posts: