-
-
Notifications
You must be signed in to change notification settings - Fork 65
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
disk mounting applet #644
Comments
A vertical listing of partitions would not fit in a narrow top or bottom panel such as 24px, which is at or near tje default. Would have to be auto-enabled on wide panels or manually enabled, perhaps by an applet context menu item. Remember also both horizontal and vertical panels are supported
|
im sory but cant it be done the way sound controler is done? lets assume main panel is bottom you click on sound icon it and it brings out vertical app widget i guess it could be done same way .. |
That would be a major rewrite and we are a small team. If someone wants to submit a PR for this w can test it of course.
Far simpler, it would become possible to set a minimum width for the applet in themes if a widget name were added to the
panel applet or to the GtkGrid (css name grid) packed within it,a similar fix would also benefit the netspeed applet.
Also note that it is now possible to center-stick an applet in mate-panel from git master, which if done with one applet whose size
changes would keep it from moving other applets.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected behaviour
it would be nice if partitions could be listed vertical ..thus avoiding panell movement when there are several panells and partitions to mount.
Actual behaviour
partitions and drives are listed horizontal thus affecting and eating panel space
Steps to reproduce the behaviour
..
MATE general version
Package version
1.26
Linux Distribution
debian bookworm
Link to bugreport of your Distribution (requirement)
its request for feature
The text was updated successfully, but these errors were encountered: