~leon_plickat/lavalauncher

v1.7.0 6 months ago

Bump to v1.7.0

Changelog:
- New display mode 'simple'. This mode should be visually identical to 'default'
  mode, however the surface is _not_ sized to span the entire edge of the output
  it is anchored to, instead it has the exact same size as the visual bar, and
  it is also only anchored to a single edge. On some compositors this may cause
  LavaLauncher to fit better onto the desktop geometrically. Also this mode
  has a smaller memory usage; Depending on screen size and bar size, the
  difference can be significant.
- When hovering over the bar, the cursor will now change. What cursor is used
  can be configured with the '-P' flag. The default is "pointing_hand".
- When setting the border width with '-S', LavaLauncher now additionally also
  accepts only a single arguments, which will set the width for all borders
  simultaneously.
- When setting the output with '-o', LavaLauncher now accepts the argument 'all'.
- When setting a colour, LavaLauncher now in addition to hex codes also accepts
  'black', 'white' and 'transparent'.
- Debug messages for output events now display the global name of the output.
  This makes it finally possible to know which event is related to which output.
- Nonsensical outputs (when width and/or height are 0) will now be ignored,
  instead of LavaLauncher exiting. Since such outputs are very likely a bug in
  the Wayland compositor, a warning message will be displayed.
- Fixed a bug causing LavaLauncher to crash when it could not connect to a
  Wayland server.
- Fixed bug causing LavaLauncher to crash when the compositor does not support
  a protocol extension it relies on, like the layer shell or XDG output. Now
  LavaLauncher correctly displays an error message and exits gracefully.
- Fixed a design oversight causing LavaLauncher to crash on some compositors
  where outputs are added before xdg_output_manager or zwlr_layer_shell are
  available.
- Fixed a design oversight that could potentially cause an unterminated string
  to be executed by a shell.
- Fixed possible memory leak.
- Lots of minor and major overhauls of the code. Things have been moved,
  rewritten, removed and redesigned to get rid of most major rough spots.
- More verbose versioning.