Allow users to specify device paths using simple wildcards in the device
path. The first matching device will be used.
For example: /sys/class/backlight/amdgpu_*
fixes#492
If an import fails, this test fails, which is not the original
intention.
Until such time that the listing of existing modules is fixed, this test
is removed.
fixes#491
Add a new parameter "output.markup" that allows a user to pass in a
custom markup string (e.g. "pango").
Note: To make use of this, the user still has to use a Pango font, as
well as use a bumblebee-status module that supports Pango output.
fixes#493
Modify the header of arch-update.py so that when using `bumblebee-status
-l modules`, the content of arch-update and batter-upower will be
separated (i.e., one more blank line between the doc of arch-update and
battery-upower).
- fix the documentation of parameters
- now also show the remaining time to fully charged when charging
- modify the code to reduce the frequency of making requests to D-Bus
The right-click popup menu in the bluetooth module does not work well in
Sway (a i3wm-compatible Wayland WM). This is known issue to
Sway. Given that the popup menu is simply to turn on/off the
bluetooth device, the graphical popup is really not necessary. This
commit adds a parameter to control whether a popup menu should be used
when a right-click happens, or we simply turn on/off the device without
the menu.
The path to object org.blueman.Mechanism was originally hard-coded to
"/". But in some systems, the path may be "/org/blueman/mechanism". So
this commit adds an extra parameter to configure the path.
Some modules (such as pulseaudio) have aliases (pasink, pasource), which
mean that the module's name might differ from it's "parent" name. To
make it possible to have shared config parameters, add a fallback that
reads the "module" parameter, if no instance parameter is found.
fixes#467
As correctly pointed out by @rrhuffy, restricting update intervals to
minutes is pretty arbitrary. Therefore, change logic to specify updates
intervals in *seconds*.
Also, to maintain backwards compatibility for users that already have
custom intervals in their config, allow a module to specify their own
"factor" for intervals. So a module that expects the interval to be in
minutes can set the factor to 60.
