Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
when changing panel orientation or rotating the screen itself,
panel might keep its old size, so some applets might appear
behind screen edge (until you restart the panel). same thing
might happen when enabling hide buttons.
fixes https://github.com/mate-desktop/mate-panel/issues/552
upstream commit with detailed problem description:
https://git.gnome.org/browse/gnome-panel/commit/?id=fc24d8fa623c4cf841eb5168cb1c250b4a84d4da
upstream commit with the actual fix:
https://git.gnome.org/browse/gnome-panel/commit/?id=4511f4466df0b163906794b4a32196226ccf90f3
yes, it's somewhat messed up there :)
|
|
This fixes menu positioning on some system tray items when the panel
orientation changed since it was initially started.
|
|
Properly forward orientation to the items. This especially fixes SNI
items height in vertical panels, but affects several other details on
SNI items.
|
|
|
|
These changes have been accidentally removed. The previously used
handler has been added to the code again, which connects to the scroll
event of the WnckPager widget.
|
|
|
|
It should only affect the space between items, not all around, and
that padding should be part of the item itself, not be outside of it.
|
|
Fixes #530.
|
|
|
|
|
|
The SNI specification doesn't explicitly state what should happen when
trying to register again an already registered item, so it would seem
only logical to forbid it. Unfortunately, libappindicator tries
re-registering pretty often, and even falls back to System Tray if it
fails. So in practice we need to be forgiving and pretend it's OK,
or we get a duplicate System Tray item for this one.
Fixes #539.
|
|
restore ability to configure launcher's custom icon which degradated after switching on g_app_info_get_icon
also update launcher state after saving launcher's properties.
|
|
This reverts commit 8c25e1bdd328a8712735c0b00cf4aede7993da1d.
LTSP no longer requires this, and it in fact prevents LTSP machines from
shutting down.
Closes https://github.com/mate-desktop/mate-panel/issues/535
|
|
|
|
|
|
|
|
|
|
|
|
Fix the logic guarding against updating the name and description so
that it properly checks against strings in the same locale.
This prevents spamming accessibility 'accessible-name' change events,
avoiding some noise when interacting with the panel.
|
|
|
|
The order was reversed when porting from the previous sorting method.
Part of #521.
|
|
This version check added to version 1.16 backport, let's use it in master too
|
|
|
|
|
|
|
|
fixes build breakage because of moved file after new tray area changes
|
|
It never was intended to be v3+ while upstream is v2+, so fix it.
|
|
|
|
|
|
|
|
It's only there because GtkImageMenuItem is deprecated, it doesn't
offer any original features.
|
|
|
|
Also, that part was quite fragile.
|
|
|
|
It makes them look a little blurry at the "proper" sizes (32, 48, etc.)
where the system-tray ones are perfect. Without the padding, they get
blurry at the same sizes system-tray ones do, not making the situation
worse.
|
|
On GTK 3.20 onwards, themes are expected to use CSS names rather than
widget class names, and apparently CSS names are not inherited. So, a
derived widget altering its CSS name won't be styled as its parent
classes.
Thus, SnItem setting the CSS name "sn-item" avoids being styled as a
"button". But on older GTK versions, the widget class being used makes
this change ineffective.
Fix that by introducing a custom derived button that doesn't draw the
unwanted parts.
|
|
|
|
|
|
The StatusNotifier part of the implementation is based off
gnome-panel's status-notifier applet.
|
|
(#515)
This patch re-purposes the existing fallback support for the now obsolete
matemenu-simple-editor to add (optional) support for menulibre. The logic is
simple, if menulibre is installed use it in preference to mozo. If menulibre
is not available, fallback to mozo.
The rationale is this; if you've installed menulibre you want to use it
in preference to mozo. Menulibre offers a superset of menu editting
capabilities compared to mozo and is growing in popularity. This change will
allow distro maintainers to chose which menu editor they want
to offer.
|
|
|
|
|
|
|
|
|
|
Force zero padding, margin, border to stop underallocation warnings.
*Note: few themes deliberately use a border here, some (notably Adwaita) inherit it from generic buttons
|
|
Force padding and margins to zero. Borders don't seem to throw warnings here
|
|
|
|
Stops negative allocation warnings unless theme sets a border
|