<feed xmlns='http://www.w3.org/2005/Atom'>
<title>tqt/src/kernel, branch fix/various</title>
<subtitle>TQt toolkit
</subtitle>
<id>https://scm.trinitydesktop.org/cgit/tqt/atom?h=fix%2Fvarious</id>
<link rel='self' href='https://scm.trinitydesktop.org/cgit/tqt/atom?h=fix%2Fvarious'/>
<link rel='alternate' type='text/html' href='https://scm.trinitydesktop.org/cgit/tqt/'/>
<updated>2024-03-29T18:31:02Z</updated>
<entry>
<title>Remove dubious screen intersection check</title>
<updated>2024-03-29T18:31:02Z</updated>
<author>
<name>Alexander Golubev</name>
<email>fatzer2@gmail.com</email>
</author>
<published>2024-03-29T18:15:59Z</published>
<link rel='alternate' type='text/html' href='https://scm.trinitydesktop.org/cgit/tqt/commit/?id=99490486e4c3ed8548e82f6c2d55a3cbc95d7cbc'/>
<id>urn:sha1:99490486e4c3ed8548e82f6c2d55a3cbc95d7cbc</id>
<content type='text'>
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 &lt;fatzer2@gmail.com&gt;
</content>
</entry>
<entry>
<title>Reset TQThreadInstance::currentThread() value when destroying main thread</title>
<updated>2024-03-29T18:31:02Z</updated>
<author>
<name>Alexander Golubev</name>
<email>fatzer2@gmail.com</email>
</author>
<published>2024-03-29T13:40:30Z</published>
<link rel='alternate' type='text/html' href='https://scm.trinitydesktop.org/cgit/tqt/commit/?id=fa52f57da125cb9003526976f53656197a930879'/>
<id>urn:sha1:fa52f57da125cb9003526976f53656197a930879</id>
<content type='text'>
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 &lt;fatzer2@gmail.com&gt;
</content>
</entry>
<entry>
<title>[DONTMERGE] Add debug tracers for TQFont and TQFontMetrics creation</title>
<updated>2024-03-29T18:31:02Z</updated>
<author>
<name>Alexander Golubev</name>
<email>fatzer2@gmail.com</email>
</author>
<published>2024-03-19T03:03:44Z</published>
<link rel='alternate' type='text/html' href='https://scm.trinitydesktop.org/cgit/tqt/commit/?id=9a94c79bd48ed053b9458212ebb9862ef90f7a7e'/>
<id>urn:sha1:9a94c79bd48ed053b9458212ebb9862ef90f7a7e</id>
<content type='text'>
Signed-off-by: Alexander Golubev &lt;fatzer2@gmail.com&gt;
</content>
</entry>
<entry>
<title>Improve TQFont-related cleanup</title>
<updated>2024-03-29T10:47:58Z</updated>
<author>
<name>Alexander Golubev</name>
<email>fatzer2@gmail.com</email>
</author>
<published>2024-03-19T02:56:36Z</published>
<link rel='alternate' type='text/html' href='https://scm.trinitydesktop.org/cgit/tqt/commit/?id=676000853b614b9063e38568e94833683bf05ccd'/>
<id>urn:sha1:676000853b614b9063e38568e94833683bf05ccd</id>
<content type='text'>
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 &lt;fatzer2@gmail.com&gt;
</content>
</entry>
<entry>
<title>TQPrinterPrivate: add virtual destructor.</title>
<updated>2024-03-20T02:24:24Z</updated>
<author>
<name>Alexander Golubev</name>
<email>fatzer2@gmail.com</email>
</author>
<published>2024-03-17T01:39:31Z</published>
<link rel='alternate' type='text/html' href='https://scm.trinitydesktop.org/cgit/tqt/commit/?id=5920542e9e62672acb42cbb70e6eac27442ebed0'/>
<id>urn:sha1:5920542e9e62672acb42cbb70e6eac27442ebed0</id>
<content type='text'>
As derivative from it e.g. TQPrinterUnixPrivate are getting deleted (e.g
in unix TQPrinter implementation) by a reference to base class.

Also added missing include to the header.

Signed-off-by: Alexander Golubev &lt;fatzer2@gmail.com&gt;
</content>
</entry>
<entry>
<title>Zero unused data fields in XClientMessageEvent struct</title>
<updated>2024-03-19T08:42:17Z</updated>
<author>
<name>Alexander Golubev</name>
<email>fatzer2@gmail.com</email>
</author>
<published>2024-03-19T05:10:08Z</published>
<link rel='alternate' type='text/html' href='https://scm.trinitydesktop.org/cgit/tqt/commit/?id=8a13d9aef40a1094723afa46dccc2ee8b52bd739'/>
<id>urn:sha1:8a13d9aef40a1094723afa46dccc2ee8b52bd739</id>
<content type='text'>
valgrind was complaining about access to uninitialized data because
unused elements in client_message.data.l array weren't set o any value.

Signed-off-by: Alexander Golubev &lt;fatzer2@gmail.com&gt;
</content>
</entry>
<entry>
<title>Zero padding bytes in DndReceiverProp struct.</title>
<updated>2024-03-19T08:42:10Z</updated>
<author>
<name>Alexander Golubev</name>
<email>fatzer2@gmail.com</email>
</author>
<published>2024-03-17T12:01:34Z</published>
<link rel='alternate' type='text/html' href='https://scm.trinitydesktop.org/cgit/tqt/commit/?id=1938504ea0884a1099dabf7fc1888af7925713f3'/>
<id>urn:sha1:1938504ea0884a1099dabf7fc1888af7925713f3</id>
<content type='text'>
This removes valgrind's complains about accessing uninitialized memory.

Signed-off-by: Alexander Golubev &lt;fatzer2@gmail.com&gt;
</content>
</entry>
<entry>
<title>Fix TQThreadStorage destruction in the main thread</title>
<updated>2024-03-18T09:36:47Z</updated>
<author>
<name>Alexander Golubev</name>
<email>fatzer2@gmail.com</email>
</author>
<published>2024-03-16T05:31:50Z</published>
<link rel='alternate' type='text/html' href='https://scm.trinitydesktop.org/cgit/tqt/commit/?id=b1e6f384640525c5a0caceef017848f8ebee46b8'/>
<id>urn:sha1:b1e6f384640525c5a0caceef017848f8ebee46b8</id>
<content type='text'>
Before that the allocations of TQThreadStorage objects from the main
thread were never destroyed and memory associated with them were never
freed. The second one isn't a huge problem as at that point program is
terminating anyway (but it still makes valgrind complain). The first one
is the bigger issue as destructors might contain some essential external
cleanups like removing temporary files.

Also make `TQApplication::guiThread()` return `0` when the thread is
destroyed (may happen on the program exiting during destruction of
statics).

Signed-off-by: Alexander Golubev &lt;fatzer2@gmail.com&gt;
</content>
</entry>
<entry>
<title>Resort includes in ntqt.h</title>
<updated>2024-03-13T00:12:36Z</updated>
<author>
<name>Alexander Golubev</name>
<email>fatzer2@gmail.com</email>
</author>
<published>2024-03-11T21:14:46Z</published>
<link rel='alternate' type='text/html' href='https://scm.trinitydesktop.org/cgit/tqt/commit/?id=b930cec6013b9609c4345268171763c2c5936ae4'/>
<id>urn:sha1:b930cec6013b9609c4345268171763c2c5936ae4</id>
<content type='text'>
Signed-off-by: Alexander Golubev &lt;fatzer2@gmail.com&gt;
</content>
</entry>
<entry>
<title>Fix compilation with -no-thread</title>
<updated>2024-03-10T13:39:03Z</updated>
<author>
<name>Alexander Golubev</name>
<email>fatzer2@gmail.com</email>
</author>
<published>2024-03-10T13:39:03Z</published>
<link rel='alternate' type='text/html' href='https://scm.trinitydesktop.org/cgit/tqt/commit/?id=4100c9e29f3ccb324a68ff1759ebbf1d35849a40'/>
<id>urn:sha1:4100c9e29f3ccb324a68ff1759ebbf1d35849a40</id>
<content type='text'>
Signed-off-by: Alexander Golubev &lt;fatzer2@gmail.com&gt;
</content>
</entry>
</feed>
