8000 module/powermenu question · Issue #655 · polybar/polybar · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

module/powermenu question #655

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

Closed
icf20 opened this issue Jul 16, 2017 · 5 comments
Closed

module/powermenu question #655

icf20 opened this issue Jul 16, 2017 · 5 comments

Comments

@icf20
Copy link
icf20 commented Jul 16, 2017

i got this

[module/powermenu]
type = custom/menu

format-foreground = ${colors.xcolor7}
format-background = ${colors.xcolor0}


label-open = "¿?"
label-open-font = 4
label-close = ""
label-close-foreground = ${colors.lime}
label-separator = " / "
label-separator-foreground = ${colors.xcolor1}


; reboot
menu-0-1 = 
menu-0-1-exec = systemctl reboot
menu-0-1-foreground = ${colors.salmon}
; shutdown
menu-0-0 = "  "
menu-0-0-exec = systemctl poweroff
menu-0-0-foreground = ${colors.salmon}

the problem i have is to move the label-close in the same place like label-open because in case of a miss click i get a power off

@patrick96
Copy link
Member

Do you have the powermenu as part of modules-center or modules-right? If so, the thing you are experiencing is that the items on the menu are added to the right of the label-open/label-close and thus the label-close appears to be shifted to the left.
Is that about right?

To avoid this problem, I have simply put the powermenu in modules-left.

There is probably no way to consistently fix this issue. One idea would be to add an option to the menu module to tell it to either add the items to the right or to the left of the label-close. This still falls short, if with all the menu items shown, the bar is too large to fit and thus some things (possibly including the closing label) are moved around. Also I don't know how it would behave, if it was part of modules-center

@icf20
Copy link
Author
icf20 commented Jul 16, 2017

Do you have the powermenu as part of modules-center or modules-right?

is on modules-right

If so, the thing you are experiencing is that the items on the menu are added to the right of the label-open/label-close and thus the label-close appears to be shifted to the left.
Is that about right?

correct

To avoid this problem, I have simply put the powermenu in modules-left

sadly that would mode the menu on the opposite part of polybar

@patrick96
Copy link
Member

Yes the menu would be on the other side of the bar, but this is currently the only way to fix this.

I am currently working on that menu option I talked about, but no promises

@icf20
Copy link
Author
icf20 commented Jul 16, 2017

i will add a confirmation via submenu and problem avoided

@icf20 icf20 closed this as completed Jul 16, 2017
@patrick96
Copy link
Member
patrick96 commented Jul 16, 2017 via email

patrick96 added a commit to patrick96/polybar that referenced this issue Jul 16, 2017
expand-right defaults to true to preserve the current functionality
If set to false, the items in the menu will be added to the left of the
toggle label (instead of the right side)

Should resolve the issue discussed in polybar#655
NBonaparte pushed a commit that referenced this issue Aug 29, 2017
expand-right defaults to true to preserve the current functionality
If set to false, the items in the menu will be added to the left of the
toggle label (instead of the right side)

Should resolve the issue discussed in #655
patrick96 added a commit to patrick96/polybar that referenced this issue Sep 4, 2017
expand-right defaults to true to preserve the current functionality
If set to false, the items in the menu will be added to the left of the
toggle label (instead of the right side)

Should resolve the issue discussed in polybar#655
patrick96 added a commit to patrick96/polybar that referenced this issue Sep 17, 2017
expand-right defaults to true to preserve the current functionality
If set to false, the items in the menu will be added to the left of the
toggle label (instead of the right side)

Should resolve the issue discussed in polybar#655
patrick96 added a commit that referenced this issue Dec 3, 2017
Breaking Changes:

* Date module no longer supports non-padded specifiers (i.e. `%-d`) and potentially other specifiers, see #792
  - Check http://en.cppreference.com/w/cpp/io/manip/put_time to see supported specifiers
* Setting background color to `background-0` with gradients (refer to https://github.com/jaagr/polybar/wiki/Known-Issues)

Changelog:

Features:
* Feat(mpd): State-specific formats (`format-playing`, `format-paused`, `format-stopped`) (#567), see #524 
* Feat(ipc): Visibility commands (show, hide, toggle, restart, quit) (b6c5563)
* Feat(shell): Bash completion (#588)
* Feat(menu): `expand-right` option (#658), see #655
* Feat(temperature): hwmon sysfs support (#688), see #404 
* Feat(cursor): Change cursors over clickable/scrollable areas (#727), see #721  
* Feat(temperature): Fahrenheit and Celsius tokens (#804)
* Feat(mpd): Use mpd name tag or URI as fallback for title-less tracks (#823), see #815 

Fixes:
* Fix(i3): Clicking workspaces without index (#521), see #520 
* Fix(parser): Prefix options overriding format options (#729), see #544
* Fix(parser): Overline tags (eebf105)
* Fix(process_util): Prefix shell environment variable (`$POLYBAR_SHELL`) (86ff947), see #566 
* Fix(parser): `%{R}` tag (reverse colors) (0bd8f1f), see #585 
* Fix(renderer): Center block position with tray (389bae2 & #673), see #551 & #672 
* Fix(xworkpaces): Active workspace with XMonad (#587), see #411 & #535 
* Fix(config): Expand tilde, environment variable (d3b0670 & #724), see #603 & #719 
* Fix(build): Remove curlbuild.h (#648), see #647 
* Fix(renderer): Off by one error for actions (#663), see #661 
* Fix(gcc): GCC 7.1 ([jaagr/xpp/#6](polybar/xpp#6))
* Fix(fs): Use `bytes_available` for `percentage_used` (138f5fa), see #710
* Fix(fs): Use `f_frsize` for calculations (a682d2a)
* Fix(date): Remove date string length limitation (#745), see #754 
* Fix(renderer): Nested actions (#772), see #760 and #758
* Fix(i3): Check and warn if current workspace not found (#826), see #824 
* Fix(github): Prevent module disappearing with no connection (#811), see #810 
* Fix(renderer): Module gradients (#831), see #759 
* Fix(build): Update deprecated jsoncpp Reader
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants
0