-
Notifications
You must be signed in to change notification settings - Fork 202
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
Feature Request: Add the ability to change whether the Media controls appears below or above the Volume controls and and the ability to control the expand direction #71
Comments
This would be hard. Moving the media transport controls to the top won't be hard but the resizing & positioning would be hard. Because "Auto height" changes only the dimension and not position. So we have to manually anchor the flyout to bottom (i.e move the flyout up/down as the height changes to make it look like anchored to the bottom) This could be a priority for v0.9?
|
And FYI, we have the ability to move the flyout since v0.1. But there were no support to save it's location & restore it after a reboot. We added support for saving it in v0.5 |
just requested on store feedback |
How ya like dis? 2021-01-11.17-48-52.mp4 |
Yes, Exactly! |
@Samuel12321:
In 0.5 we added the ability to change where on the screen the flyout appeared, however if the user moves the flyout to the bottom of the screen, the media flyout can go off the screen.
@jean3x7:
I want to dock the flyout to the bottom without the content being hidden
Current behaviour:


Proposed behaviour:


The text was updated successfully, but these errors were encountered: