General and Desktop

@Christian-Ehrlicher said in QObject's QThread from shared library: You must be doing something in your Tester ctor. In the code above you can see that there is totally empty ctor :) But looks like that I have found the issue. Need to check it tomorrow.

@CarlB said in Python / PySide6 - swipe gesture?: Hi - while I've disabled the setting, its a little awkward... to put into context, a friend of mine has ended up vibe-coding a similar songbook program - this is done in javascript, and he's able to swipe to next song with a single finger - I find it odd to see that I python / qt can't do something similar...? Does in javascript mean in a web browser? You can, but QSwipeGesture doesn't provide it out of the box. start from QSwipeGestureRecognizer in qtbase/src/widgets/kernel/qstandardgestures.cpp and create a modified version of QSwipeGestureRecognizer::recognize to require 1 instead of 3 touch points. Use a pan gesture instead. Embed a web view, and implement the swipe logic there in javascript. Quick SwipeView or SwipeDelegate might be more appropriate.

@SGaist said in Freezing issue caused by socket and UI updates in the thread and main thread: Remove that infinite loop -> Qt is event driven so grab the data when it arrives then trigger the processing That for check crc void UdpSocket::processIncomingDatagram() { static const QByteArray magic("\x55\xAA\x55\xAA", 4); while (true) { const int pos = m_buffer.indexOf(magic); if (pos < 0) { m_buffer.clear(); break; } if (pos > 0) m_buffer.remove(0, pos); if (m_buffer.size() < 8) break; const quint32 len = qFromBigEndian<quint32>(reinterpret_cast<const uchar*>(m_buffer.constData() + 4)); if (m_buffer.size() < 8 + static_cast<int>(len)) break; const QByteArray frame = m_buffer.left(8 + static_cast<int>(len)); if (!calculateCrc(frame)) { m_buffer.remove(0, 1); continue; } parseData(frame); m_buffer.remove(0, 8 + static_cast<int>(len)); } } @SGaist said in Freezing issue caused by socket and UI updates in the thread and main thread: If the data is "too fast" then there's no sense in trying to show it all the time, your users won't be able to see all these changes (it's like trying to show a billion points -> useless). Batch the updates at a rate that is useful. I also use decimation for points. @SGaist said in Freezing issue caused by socket and UI updates in the thread and main thread: Also, there's no need to subclass QUdpSocket, you just use it thus avoid subclassing in this case. no no no my UdpSocket class is QObject

@ChrisA said in Qt Creator takes CPU 100% when IDE terminates: Any resolution? I'm having this on macOS with Qt Creator 19.0.2. After quitting, Activity Monitor shows CPU at 100% until I force-quit. Same issue here on macOS with Qt Creator 19.0.2 — following this thread in case anyone finds a fix.

@Chris-Kawa said in QPalette is useless after QSS: QSS does not overwrite palette. Of course it does not change the current palette itself. But it changes the current appearance of the active palette by adding modifications to it. If that makes sense. This is what I mean above.

We started with this style sheet (it's been a while ago, so it might have changed in the meantime): https://github.com/colinduquesnoy/qdarkstylesheet We just grabbed the .qss and the necessary icons from that repository. This was because we wanted to have a dark style (and at first used the default light mode of Qt on Windows). Qt didn't have a dark mode back then. Then we searched for all the different colors that are used. Here are the colors we have found (and maybe even changed some colors): BACKGROUND ----------- Light #4D545B #505F69 (unpressed) Normal #31363B #32414B (border, disabled, pressed, checked, toolbars, menus) Dark #232629 #19232D (background) FOREGROUND ----------- Light #EFF0F1 #F0F0F0 (texts/labels) Normal #AAAAAA (not used yet) Dark #505F69 #787878 (disabled texts) SELECTION ------------ Light #179AE0 #148CD2 (selection/hover/active) Normal #3375A3 #1464A0 (selected) Dark #18465D #14506E (selected disabled) Each occurrence of a color we replaced with %1, %2, %3, etc. in the style sheet. If we want to apply either light mode or dark mode we load the style sheet as string and replace the dark or light colors with QString::arg() and then apply the style sheet.

@Christian-Ehrlicher didn't seen that at first but was wondering about the table containing all default icons and their names and changing their size.

dear op: there is a difference in TCP syn reject vs tcp syn drop. The reject would send a (nak) signal back.. the dropping would leave the sender unknowing whether the recipient ever received the syn signal in the first place. I think you need to re-look at your methodology for determining whether the server is "available". I'm less inclined to believe it is a QT framework bug. You may need to do a deep dive on the QAbstractSocket::SocketError type and understand exactly why each of those conditions can occur, and react accordingly.

@SGaist oooohh right. oversaw the %1 in the path. yeee gonna put something there for the user warning when i got the other things done!

@Simmania With Qt Creator 20 you can use the ACP Client to connect to an ACP Agent like Claude Agent, Codex CLI, or OpenCode and do any AI work. The ACP Client plugin is part of the OpenSource Qt Creator.

@SimonSchroeder Ahh ok that's much easier than what I am doing now. Thank you!

Alright, thank you for your suggestion. I'll give it a try

So it's the windowsvista style. I can reproduce it but no idea how to fix it. You might create a bug report -> bugreports.qt.io

Or, more likely it was the dumb mistake of doing a quick hack for testing, which deleted my test object...

HoverHandler has a point property which has a position property. Alternatively since you are implementing your QQFBO in c++ you can override hoverMoveEvent and handle it there (after calling setAcceptHoverEvents).

@jeremy_k said in Qt Widgets or Qt Quick/QML for this application?: @Simmania said in Qt Widgets or Qt Quick/QML for this application?: plus the OSG stuff This might be a misunderstanding. The Qt Quick 2 scene graph isn't OpenSceneGraph. Sorry, I ment the QSG.

To add to @jeremy_k KDE folks also implements that technique in their libraries/software.

@JonB said in Need a canvas like widget: QMainWindow is a containing widget with a complex layout as shown in the pic. You could create something like it yourself with parent-child widgets and layouts --- so it is not "magic" --- but it's convenient to use it for just the layout you want. Make the central widget be whatever for your canvas and its relative coordinates will be used for anything you place on it. The menu and status bars will not overlap or interfere with its coordinates. Well, as it turned out, I did already have a QMainWindow, but wasn't aware of what it actually provides, so I got mself a QMainWindow and then explicitly created a QMenuBar inside rather than using the already provided w->menuBar(); (*w is my QMainWindow). I now do w->setCentralWidget(new QWidget); Canvas *Drawingarea = new Canvas(w->centralWidget()); and Bob's my father's brother. Reading (in Germany we have a saying that "Whoever can read has a definite advantage") the documentation about QMainWindow, it is actually exactly what I need!