From f3312751b999d90645180d5211f6997a858465d0 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Stephan=20A=C3=9Fmus?= Date: Tue, 8 Jul 2008 22:31:26 +0000 Subject: [PATCH] honor 80 char limit in comment git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@26331 a95241bf-73f2-0310-859d-f6bbb57e9c96 --- src/kits/interface/View.cpp | 17 ++++++++++------- 1 file changed, 10 insertions(+), 7 deletions(-) diff --git a/src/kits/interface/View.cpp b/src/kits/interface/View.cpp index 2359883f37..07c42eb9a0 100644 --- a/src/kits/interface/View.cpp +++ b/src/kits/interface/View.cpp @@ -1440,13 +1440,16 @@ BView::GetMouse(BPoint *location, uint32 *buttons, bool checkMessageQueue) // TODO: ServerWindow replies with an int32 here ConvertFromScreen(location); - // TODO: in beos R5, location is already converted to the view local coordinate system, - // so if an app checks the window message queue by itself, it might not find what it expects. - // NOTE: the fact that we have mouse coords in screen space in our queue avoids the problem - // that messages already in the queue will be outdated as soon as a window or even the - // view moves. The second situation being quite common actually, also with regards to - // scrolling. An app reading these messages would have to know the locations of the window - // and view for each message... otherwise it is potentially broken anyways. + // TODO: in beos R5, location is already converted to the view + // local coordinate system, so if an app checks the window message + // queue by itself, it might not find what it expects. + // NOTE: the fact that we have mouse coords in screen space in our + // queue avoids the problem that messages already in the queue will + // be outdated as soon as a window or even the view moves. The + // second situation being quite common actually, also with regards + // to scrolling. An app reading these messages would have to know + // the locations of the window and view for each message... + // otherwise it is potentially broken anyways. } else *buttons = 0; }