tqt/src, branch fix/variousTQt toolkit
https://scm.trinitydesktop.org/cgit/tqt/atom?h=fix%2Fvarious2024-03-29T18:31:02ZRemove dubious screen intersection check2024-03-29T18:31:02ZAlexander Golubevfatzer2@gmail.com2024-03-29T18:15:59Zurn:sha1:99490486e4c3ed8548e82f6c2d55a3cbc95d7cbc
On a non-xinerama (user-side) configuration it is straight up wrong, as
in such case each screen's coordinates start at 0:0. Which makes the
apps on the smaller screen assume incorrect screen size.
And on a xinerama config it is incorrect as well as it results in access
past allocated data in rects and screen arrays.
Signed-off-by: Alexander Golubev <fatzer2@gmail.com>
TQRegExp: fix engine cache destruction ordering2024-03-29T18:31:02ZAlexander Golubevfatzer2@gmail.com2024-03-29T17:08:19Zurn:sha1:65f9e94fca17d1c412ed944af328ae14871078b3
In case there are static TQRegExp instances the regexp engine cash might
be destroyed before them; hence we need some special handling of
construction/destruction of the cache objects.
Signed-off-by: Alexander Golubev <fatzer2@gmail.com>
TQTextCodec: avoid dangling pointer to current locale's codec2024-03-29T18:31:02ZAlexander Golubevfatzer2@gmail.com2024-03-29T15:14:14Zurn:sha1:10bd40911eed8b1bc37d56797c46d52f4357bc65
This fixes crashes cause by dangling pointer returned from
TQTextCodec::codecForLocale(). That might happen when tqWarning() and
such are called during final cleanup.
Signed-off-by: Alexander Golubev <fatzer2@gmail.com>
Reset TQThreadInstance::currentThread() value when destroying main thread2024-03-29T18:31:02ZAlexander Golubevfatzer2@gmail.com2024-03-29T13:40:30Zurn:sha1:fa52f57da125cb9003526976f53656197a930879
This assures that TQRegExp who checks if there is an active thread
through this interface won't try to access its already destroyed
TQThreadLocalStorage, which might happen during destruction of static
TQRegExp objects.
Bug: https://mirror.git.trinitydesktop.org/gitea/TDE/tqt3/issues/142
Signed-off-by: Alexander Golubev <fatzer2@gmail.com>
TQTextEdit: remove one of two readOnly flags2024-03-29T18:31:02ZAlexander Golubevfatzer2@gmail.com2024-03-19T05:37:25Zurn:sha1:34dbe21c8d3dae60f93a0ebcb475fb1024466c34
There were two flags for read-only with different capitalization:
readonly and readOnly. This was probably a mistake.
Signed-off-by: Alexander Golubev <fatzer2@gmail.com>
TQTextEdit: add missing mightStartDrag initialization2024-03-29T18:31:02ZAlexander Golubevfatzer2@gmail.com2024-03-19T05:32:55Zurn:sha1:4035e1b59e2fd8797e34c33dd27321ec9bab6368
mightStartDrag might have been used uninitialized when moving mouse with
pressed mouse button into window.
Signed-off-by: Alexander Golubev <fatzer2@gmail.com>
[DONTMERGE] Add debug tracers for TQFont and TQFontMetrics creation2024-03-29T18:31:02ZAlexander Golubevfatzer2@gmail.com2024-03-19T03:03:44Zurn:sha1:9a94c79bd48ed053b9458212ebb9862ef90f7a7e
Signed-off-by: Alexander Golubev <fatzer2@gmail.com>
Improve TQFont-related cleanup2024-03-29T10:47:58ZAlexander Golubevfatzer2@gmail.com2024-03-19T02:56:36Zurn:sha1:676000853b614b9063e38568e94833683bf05ccd
Improve TQFont cleanup making sure that all instances of TQFont are
destroyed before TQApplication (or specifically before disconnect from
X11). This gets reed of several valgrind complains about leaks deep
inside fontconfig.
Signed-off-by: Alexander Golubev <fatzer2@gmail.com>
TQFileDialog: cleanup pixmaps before destroying TQApplication2024-03-22T01:11:47ZAlexander Golubevfatzer2@gmail.com2024-03-19T03:56:14Zurn:sha1:fb0d62eec811ab2d4d73550e455944cecbe7e091
Otherwise it results in small memmory leakage on exit of Xlib data.
Signed-off-by: Alexander Golubev <fatzer2@gmail.com>
TQPrintDialog: cleanup data requested from libcups2024-03-21T00:14:58ZAlexander Golubevfatzer2@gmail.com2024-03-19T06:27:28Zurn:sha1:c2c385eef261e8bba46d360ceccdb604733f07c0
Signed-off-by: Alexander Golubev <fatzer2@gmail.com>