-
Notifications
You must be signed in to change notification settings - Fork 26.7k
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
CupertinoPageRoute/Transition triggered by swipe back using magic keyboard trackpad #148609
Comments
It seems to work well in Flutter master version (3.22.0-36.0.pre.48). |
@mark8044 Check above comment and see if it helps in your case or not. |
@darshankawar Hi for me it does not seem to work. It will actually swipe forward and back on the listview that's on the screen (revealing some actions I have setup when you swipe left-right on the listview), but it will not actually try to close the window @intelryzen Is there any special setup or coding you did to get the keyboard trackpad to behave that way for you? |
@mark8044 Thanks for the feedback. Can you provide us a minimal reproducible code sample that shows the current behavior you are reporting ? |
@darshankawar Hi, Im not sure what code to post here, because the functionally would be baked into the CupertinoPageRoute/Transition, meaning the end user would not have to do anything (same as with making a screen swipe back/closed). However, maybe there is something simple I can implement to make this work as @intelryzen seems to say it works for him. I'll await and see if he has tips/pointers Thanks much |
@intelryzen Can you provide here the implementation that shows the use case works ? |
Use case
Swipe back to close a page on iPhone/iPad works flawlessly, however it does not seem to be triggered via the trackpad on a Magic Keyboard (or other iPad accessory keyboards).
Proposal
Ideally, swiping left or right on the accessory keyboard's trackpad would trigger the CupertinoPageRoute/Transition just as if the screen was directly swiped
The text was updated successfully, but these errors were encountered: