From 72cd1c77266abc6223f558773cf8e11a9bb04b40 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Stephan=20A=C3=9Fmus?= Date: Thu, 9 Apr 2009 14:05:31 +0000 Subject: [PATCH] Fixed some weird fallback code, I don't think it's used and added a TODO for whoever stumbles there next... git-svn-id: file:///srv/svn/repos/haiku/haiku/trunk@30067 a95241bf-73f2-0310-859d-f6bbb57e9c96 --- src/kits/tracker/PoseView.cpp | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/src/kits/tracker/PoseView.cpp b/src/kits/tracker/PoseView.cpp index 4424025548..fa8530a376 100644 --- a/src/kits/tracker/PoseView.cpp +++ b/src/kits/tracker/PoseView.cpp @@ -8093,15 +8093,19 @@ BPoseView::Extent() const void BPoseView::SetScrollBarsTo(BPoint point) { - BPoint origin; - if (fHScrollBar && fVScrollBar) { fHScrollBar->SetValue(point.x); fVScrollBar->SetValue(point.y); } else { - origin = LeftTop(); - ScrollTo(BPoint(point.x, origin.y)); - ScrollTo(BPoint(origin.x, point.y)); + // TODO: I don't know what this was supposed to work around + // (ie why it wasn't calling ScrollTo(point) simply). Although + // it cannot have been tested, since it was broken before, I am + // still leaving this, since I know there can be a subtle change in + // behaviour (BView<->BScrollBar feedback effects) when scrolling + // both directions at once versus separately. + BPoint origin = LeftTop(); + ScrollTo(BPoint(point.x, point.y)); + ScrollTo(point); } }