Select Git revision
Search by author
- Any Author
- authors
-
Administrator root
-
Alaric Senat
asenat
-
Alexandre Janniaux alexandre-janniaux
-
Bart - The Review Bot
Bart
-
Benjamin Arnaud
bunjee
-
Christophe Massiot cmassiot
-
Claudio Cambra
claucambra
-
David dfuhrmann
-
Denis Charmet
typx
-
Fatih Uzunoğlu fuzun
-
Felix Paul Kühne
fkuehne
-
François Cartegnie
fcartegnie
-
Gabriel Lafond-Thenaille gabriel_lt
-
**** project_435_bot
-
**** project_435_bot_867220ea9cbb40f38051abad33491375
-
Ilkka Ollakka
ileoo
-
Jean-Baptiste Kempf
jbk
-
Jean-Paul Saman
jpsaman
-
Johannes Kauffmann
JohannesKauffmann
-
Konstantin Pavlov
thresh
- Jan 29, 2022
-
-
also, do the "undefined" entry of another option.
-
-
-
the integer mapping should not appear like this in these labels. it just creates a mess. it is the job of the CLI interface to show the values besides this text such as to give users this mapping. in GUIs showing users this mapping is completely unwanted. these now happen to be identical to those in sdiout and thus consistent and would reduce translator burden if translated in future.
-
-
-
-
and move to define like the rest.
-
took the opportunity to change "opengl" to "OpenGL" since that is more appropriate for how it is used in interfaces, and to use defines as commonly done for cleanliness.
-
(Excluding the 'general' subcats which come first). For neatness only. (No functional difference).
-
To make the file contents neater. Essentially: - The title defines have been grouped at the top. - A new group of tooltip defines introduced by !1172 will follow this once that MR has merged. - Then we have the help text defines, grouped per category, with the unnecessary empty lines between them removed. The titles relate to both simple prefs view tabs, and advanced view cat & subcat node labels, and furthermore the panel titles of general subcats. The tooltips relate to simple prefs view tabs only. The help text, for subcats, is used on advanced view panels. Some are only associated with cats and are actually unused currently.
-
We have no need at all for these to be defines, which just adds unnecessary clutter. They are all very short and it is much tidier with the text merged into the table.
-
...and useless comment.
-
- Jan 28, 2022
-
-
The m4 file is a dependency of lib-prefix, leading to error at bootstrap because it was missing after update from commit 32b3f47b. configure.ac:618: warning: gl_HOST_CPU_C_ABI_32BIT is m4_require'd but not m4_defun'd m4/lib-prefix.m4:155: AC_LIB_PREPARE_MULTILIB is expanded from... m4/lib-link.m4:181: AC_LIB_LINKFLAGS_BODY is expanded from... m4/iconv.m4:10: AM_ICONV_LINKFLAGS_BODY is expanded from... m4/gettext.m4:55: AM_GNU_GETTEXT is expanded from... configure.ac:618: the top level configure.ac:618: warning: gl_HOST_CPU_C_ABI_32BIT is m4_require'd but not m4_defun'd m4/lib-prefix.m4:155: AC_LIB_PREPARE_MULTILIB is expanded from... m4/lib-link.m4:181: AC_LIB_LINKFLAGS_BODY is expanded from... m4/iconv.m4:10: AM_ICONV_LINKFLAGS_BODY is expanded from... m4/gettext.m4:55: AM_GNU_GETTEXT is expanded from... configure.ac:618: the top level autoreconf: configure.ac: tracing configure.ac:618: warning: gl_HOST_CPU_C_ABI_32BIT is m4_require'd but not m4_defun'd m4/lib-prefix.m4:155: AC_LIB_PREPARE_MULTILIB is expanded from... m4/lib-link.m4:181: AC_LIB_LINKFLAGS_BODY is expanded from... m4/iconv.m4:10: AM_ICONV_LINKFLAGS_BODY is expanded from... m4/gettext.m4:55: AM_GNU_GETTEXT is expanded from... configure.ac:618: the top level
-
-
-
-
-
already done within the functions being called.
-
...with `NSTR()` to prevent unwanted assessment in translatable string searches, as per the previous commit. note that in a few cases it might actually be wrong for translation to be occurring, which will be addressed separately in the next commit(s).
-
essentially the macos side of 6cd08480, as requested in !1172 discussion. the new `NSTR()` macro is the equivalent of `qfut()`. it is intended for use instead of `_NS()` when wrapping a define name, variable or function call, where the system that scans for strings we want to be translated should not apply, leaving `_NS()` to just be used for marking such strings. i have avoided renaming `_NS()` to avoid unnecessary widespread change.
-
Provide the context in which the vdpau and OpenGL functions can be found to ensure we are using initialized pointers. In particular, it now uses the sys before it's set to the interop->priv part, instead of dereferencing NULL. Regression from b42d8e9e. Fix #26553 Co-authored-by:
François Cartegnie <fcvlcdev@free.fr>
-
François Cartegnie authored -
This is the same value set when compiling the contribs.
-
We don't know exactly which compatibility is allowed or not. It doesn't hurt to rebuild when we're not sure. And then we can use the PROTOBUF_VERSION variable consistently.
-
Otherwise it won't compile compatible code. If protoc is not there we check the version of protobuf we expect so we get the proper error messages on what's really missing.
-
Similar to how we force detection of luac there. We might be using AC_CHECK_TOOL(PROTOC, protoc, no, [${CONTRIB_DIR}/../bin$PATH_SEPARATOR$PATH]) Which works, but it doesn't keep the full path, so if the PATH is not set in the environment when using HOST-protoc it doesn't find it. So we either have to force everyone to add a new item in their PATH or just use the transparent way that luac is using. -
Similar to how we use $host-luac that we build natively.
-
Since we built protobuf we also need the matching protoc. This is the same as we do for luac. +factorize some calls to make .luac .protoc
-
It's better handled in contribs were the versions is the same and the system package detection is better. So do not force the rebuild of it in snap.
-
We check if protoc is in the path with the version we want, otherwise we build it. It is extracted "manually" to protoc-VERSION-cpp so it can be built in parallel with protobuf. They don't use each other.
-
Same patch that is in extra/tools with the original patch header.
-
-
-
It takes a lot of time for something we don't use.
-
The patch doesn't apply and is discarded. A similar fix exists in the version we use.
-
- Jan 27, 2022
-
-
widget would normally require WindowTransparentForInput, without this we end up with an invisible area within our window that grabs our mouse events. But using this this causes rendering issues with some VoutDisplay (xcb_render for instance) instead, we manually, set a null intput region afterwards (see setTransparentForMouseEvent)
-
-
Using the explicit type make the variable be assigned by pointer, but it is assigned by value which gives the error > Error: Cannot assign DialogId to DialogId*
-
Types are used in connections, they must be registered with both Q_DECLARE_METATYPE and qRegisterMetaType as stated in the documentation. > To use the type T in QVariant, using Q_DECLARE_METATYPE() is sufficient. > To use the type T in queued signal and slot connections, > qRegisterMetaType<T>() must be called before the first connection > is established.
-
