Age | Commit message (Collapse) | Author | Files | Lines |
|
This code got introduced with 3c21f66bf30810fcb25dfe8c3c0960df270dc416
trying to mimic `gdk_spawn_on_screen()`, but does not: what
`gdk_spawn_on_screen()` did (on X11) was to append the screen number to
the display, so that it worked on a multi-screen setup where the app is
not on the default X screen.
However, the code that got introduced just sets the display, which is
gonna be already there anyway (yet possibly loosing the default screen
in the process?), and AFAIK GDK dropped support for multi-screen setups
anyway (not to be confused with multi-monitor with e.g. Xinerama).
We should actually be better of without any of this, as it most likely
doesn't do what it is supposed to, nobody needs what it failed to do,
and it breaks XWayland on Wayland.
Fixes #1387.
|
|
cppcheck tells us that we perform NULL checking inconsistently, and
reports a potential NULL dereference. Here however the string cannot
be NULL, so just drop the unnecessary check.
> mate-panel/panel-run-dialog.c:1663:10: warning: Either the condition '!start' is redundant or there is possible null pointer dereference: start. [nullPointerRedundantCheck]
> while (*start != '\0' && g_ascii_isspace (*start))
> ^
> mate-panel/panel-run-dialog.c:1679:6: note: Assuming that condition '!start' is not redundant
> if (!start || !start [0]) {
> ^
> mate-panel/panel-run-dialog.c:1663:10: note: Null pointer dereference
> while (*start != '\0' && g_ascii_isspace (*start))
> ^
|
|
This is *not* an issue, as it's not really a bounds check but a mere
limit, and the array is NULL-terminated.
However, it looks odd and cppcheck (unsurprisingly) doesn't understand
the details well enough and reports this as a misordered bounds check.
> mate-panel/panel-run-dialog.c:166:12: style: Array index 'i' is used before limits check. [arrayIndexThenCheck]
> items[i] && i < history_max_size;
> ^
|
|
* panel-run-dialog: Add accelerator keys for "list of known applications" in panel run dialog, display modifier keys by using GtkCellRendererAccel
* fixup! panel-run-dialog: Add accelerator keys for "list of known applications" in panel run dialog, display modifier keys by using GtkCellRendererAccel
* fixup! fixup! panel-run-dialog: Add accelerator keys for "list of known applications" in panel run dialog, display modifier keys by using GtkCellRendererAccel
* fixup! fixup! fixup! panel-run-dialog: Add accelerator keys for "list of known applications" in panel run dialog, display modifier keys by using GtkCellRendererAccel
* fixup! fixup! fixup! fixup! panel-run-dialog: Add accelerator keys for "list of known applications" in panel run dialog, display modifier keys by using GtkCellRendererAccel
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
cppcheck --enable=all . 2> err.txt
grep variableScope err.txt
|
|
The gtk_tree_model_get() duplicates memory or adds a reference
and any data need to be freed explicitly.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
origin commits:
https://git.gnome.org/browse/gnome-panel/commit/?h=gnome-3-4&id=9fca67f
https://git.gnome.org/browse/gnome-panel/commit/?h=gnome-3-4&id=695d30c
https://git.gnome.org/browse/gnome-panel/patch/?id=00f9870cb28e6ef657d1
|
|
|
|
avoids jumping of nearby UI controls when icon is bigger than requested
|
|
learning signal chaining...
|
|
fix #676
|
|
in HiDPI
|
|
fix #296
|
|
introduced in 7f99492c269f541c81e4f36742ecc3f0b4ebac04
|
|
|
|
*Fix scaling of panel widgets, buttons, and the menu bar
*Draw grab handles at the ends of the panel
*Fix size of _almost_ all included applets
*Fix panel snapping coordinates
*Down-scale monitor coordinates to support multi-monitors
Author: Victor Kareh <[email protected]>
Date: Wed Dec 20 14:03:18 2017 -0500
|
|
Fix https://github.com/mate-desktop/mate-panel/issues/706
*patch by https://github.com/muesli4
|
|
|
|
|
|
A setting is added to show the run dialog history in reverse.
|
|
In a special case where the history size was 1, the actual history saved
had length 2. In addition history is always written with new entries.
One could also connect a signal to the max size property to force
writing history (i.e., to shorten it).
|
|
A key has been added to the gsettings schema that controls history size.
The code of the run dialog has been changed to use that key.
|
|
Initially the org.mate.panel.general.history-mate-run key was saved with
the most recent command last. In combination with wrong code this led to
scrambling the history.
This commit changes the history storage in a way that most recent
elements are stored first. The code adapts to this change by changing
only one function to prepend instead of append in the list store. (Any
old histories might therefore be wrong for a short time, but that's
probably worth it to fix this bug.)
|
|
once it was some easter egg, now it's just a non-working garbage
|
|
and require libmate-desktop >= 1.17
WARNING: use GTK+3 build of libmateweather for this build.
that lib is not migrated to GTK+3 only as we will possibly
use libgweather instead of it.
|
|
|
|
|
|
|
|
|
|
Instead of writing some long line again and again, use a small helper.
Taken from gnome-panel commit: 412ac2e4fa6a19c454b7046b9f57b9622a7b97d0
From: Vincent Untz <[email protected]>
|
|
Based on gnome-panel commit: b4deac9d217b4785d2c930a2deb2d94f5e4878d9
From: Carlos Garcia Campos <[email protected]>
|
|
|
|
|
|
|
|
|
|
|