-
Notifications
You must be signed in to change notification settings - Fork 28.6k
Update dual scrollbar constructor to support corner space #122345
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I was looking into this as part of a school project (I have no experience contributing to open source) and I was wondering if this issue needs to be updated. I noticed that the dual factory method for the Cupertino Scrollbar was never merged into main so was not sure how to proceed since I can't add to that. Just curious. |
Hey @Piinks, do you have a sample app for this problem? I by myself was not even able to get the two scrollbars 😓 My code example```dartimport 'package:flutter/material.dart'; void main() { class MainApp extends StatelessWidget { @OverRide
|
Hello I am Ajay, I am new to open-source contribution, But I am very interested in resolving issues Can you please explain to me briefly How to resolve good first issues |
Sorry to bother, I'm aware the Flutter teams has their hands full right now, but I have been waiting for this since 2D scrolling was announced, I would like to ask, is there any development about corner spaces so far? |
Uh oh!
There was an error while loading. Please reload this page.
Part of the 2D scrolling proposal: flutter.dev/go/2D-Foundation
#122349 adds a factory constructor that creates two scrollbars for scrolling in two dimensions. This change is proposed as a lead up to
TwoDimensionalScrollable
etc.The dual factory constructor works almost perfectly when plugged into
TwoDimensionalScrollable
, except for the small overlap in the joining corner.While investigating this, I found multiple native behaviors. Most common:
Both of these should be supported.
I have investigated this a fair bit, and I think the best way for this to work (instead of creating two instances of the scrollbar widget) is to have the
.dual
constructor instead create two instances of ScrollPainter internal to the single scrollbar widget.This is because in order to properly avoid overlapping each other, the painters need to know about the state of each other since the scrollbar size and visibility can change based on hovering, dragging, whether or not scrolling is happening, etc.
The text was updated successfully, but these errors were encountered: