Apache OpenOffice (AOO) Bugzilla – Issue 77549
Scrollbar - vcl control areas not correctly superposed with aqua areas on scrollbar
Last modified: 2008-07-10 11:46:02 UTC
Pagedown, then click line up where the up arrow is on the "Windows" scrollbar, at the top. Even though there is no arrow, a line up occurs. Click in the line up button at the bottom - a page down occurs.
keyword
The horizontal behavior has the same behavior - like the left arrow is at the left and not at the right.
Reassign to me, add Ismael on CC
After an interesting discussion with Philipp Lohmann, I Think I got it : the offset is equal to the buttons width, and to solve the issue, we should translate vcl ThumbRect position when DoubleMax Apple scrollbar variant is used. I have created isAppleScrollBarVariantDoubleMax() to help. Next step to fix this issue : find how move that Thumb Rectangle
*** Issue 79182 has been marked as a duplicate of this issue. ***
*** Issue 79637 has been marked as a duplicate of this issue. ***
I did some progress, and I'll commit a (not final) change in aquavcl03
Changes commited in aquavcl03. After a lot of tries, give the correct rectangle position in getNativeControlRegion() does _not_ work. I'll continue and try to see where there is a problem ( probably something bad in scrbar.cxx )
last changes have been commited in aquavclcarbonfixes cws - Scrollbar variant is checked at launch, and value is now stored in saldatas - kEventAppearanceScrollbarVariantChanged is now used, allowing the scrollbar variant to be modified in runtime All issues are not fixed. To be continued
Fixed in CWS aquavclcarbonfixes.
Issue verified fixed
Reopening. Issue is NOT fixed in m229.
In to-be-m229, you can't drag the scroll thumb in the lower half and drag it to the top.
*** Issue 82829 has been marked as a duplicate of this issue. ***
fixed in aquavcl04
ok, I think I got it now. The fix involves more magical values, however (similar to what eric tries in the first place). last batch of fixes committed to aquavcl04
This issue is correctly fixed Verified on Leopard and Tiger on both Intel, and PowerPC -> Issue verified fixed.
closing