Commits on Source (26)
-
Debarshi Ray authored
This makes it convenient to use raw gpointers as values. eg., when stuffing booleans and integer values as pointers in the cache. https://gitlab.gnome.org/GNOME/libdazzle/-/merge_requests/49
1c0903a6 -
Debarshi Ray authored
This will let users rely on the changes introduced in the previous commit. https://gitlab.gnome.org/GNOME/libdazzle/-/merge_requests/49
920908d1 -
Christian Hergert authored
task-cache: Allow NULL as value_copy_func and value_destroy_func See merge request GNOME/libdazzle!49
3915b264 -
Debarshi Ray authored
The g_assert macro can be turned off by defining G_DISABLE_ASSERT. Therefore, it's not meant to be used in unit tests because the tests will be ineffective if compiled with G_DISABLE_ASSERT. In addition to that, g_assert_true and friends emit a more human readable error message in case the condition is not satisfied. https://gitlab.gnome.org/GNOME/libdazzle/-/merge_requests/50
c317be19 -
Christian Hergert authored
tests: Don't use g_assert See merge request GNOME/libdazzle!50
c78c95b3 -
Philipp Kiemle authoredf933d2ab
-
Biswapriyo Nath authored7a427010
-
Christian Hergert authored
Include counter headers not for Win32. See merge request GNOME/libdazzle!51
ad7fd089 -
Claes Nästén authored
munmap on Solaris 10, depending on compile time defines can use caddr_t instead of void* as its argument failing the build with the following error message: error: passing argument 1 of 'munmap' from incompatible pointer type cast to void*, should be safe.
b33d4309 -
Christian Hergert authored
build: fix build on Solaris 10 with GCC 8.4 See merge request GNOME/libdazzle!52
3fe587ff -
Tom Schoonjans authored
Since this will add some objective-c code to the build, compilation must then occur with the -xobjective-c flag.
62eb1867 -
Christian Hergert authored
build: set PLATFORM_OSX on macOS See merge request GNOME/libdazzle!53
a6904fa8 -
Tom Schoonjans authored
These flags break the build on Windows, where __GNUC__ is not defined and checked for in the glib headers
6d551056 -
Tom Schoonjans authoredbe092c50
-
Tom Schoonjans authored1666a2ba
-
Tom Schoonjans authored9758e49a
-
Tom Schoonjans authorede2328892
-
Tom Schoonjans authored
Doing so messes up the installation on Windows, where the dlls go into the bindir, where the import libraries go into the libdir
e6ec1613 -
Christian Hergert authored
Fix build on Windows See merge request GNOME/libdazzle!54
7f57fca1 -
Christian Hergert authored
Not really all that helpful, and just causes signed warnings on some platforms. Fixes #58
08c4ac87 -
Christian Hergert authored
Followup to !54
2cbdbe1a -
Boyuan Yang authoredc36065ac
-
Vanadiae authored
Currently when moving the focus with the keyboard (tab, arrow keys), the focus always moves in the Tab direction, without ever following what focus move direction was requested. This is because the DzlDockWidget tells it supports receiving the keyboard focus, which is not the case: it is not e.g. a button or entry, instead it's more a dock container than anything else. So this commit fixes it by dropping the line that set the can-focus property to True.
48af7038 -
Christian Hergert authored
dzl-dock-widget: Don't set can-focus to True See merge request GNOME/libdazzle!55
a4336462 -
Christian Hergert authored22b34014
-
Jeremy Bicha authoredb8949d2e
po/de.po
0 → 100644
po/zh_CN.po
0 → 100644