General and Desktop

@In-Fo Take a look here: https://doc.qt.io/qt-5/why-moc.html Usually you do not have to care about it as QMake will do. It will add instructions to the makefiles to generate, build and link moc files. In your case it seems not to happen for what ever reason. You can post the whole build log.

Sounds like you should not be using QSerial and instead design a custom solution outside of Qt. Qt is not for real-time processing and your description of the task seems to imply real-time constraints.

I found out that I can reproduce this behavior by setting QT_DISTANCEFIELD_DEFAULT_BASEFONTSIZE, QT_DISTANCEFIELD_DEFAULT_SCALE and QT_DISTANCEFIELD_DEFAULT_RADIUS variables. With these, the problem occurs even on Windows. Not sure whether it's the same problem or not, but if QT_DISTANCEFIELD_DEFAULT_RADIUS is NOT DIVISIBLE by QT_DISTANCEFIELD_DEFAULT_SCALE, the problem occurs 100% of time (some letters will disappear). Example: export QT_DISTANCEFIELD_DEFAULT_BASEFONTSIZE=128 export QT_DISTANCEFIELD_DEFAULT_SCALE=12 export QT_DISTANCEFIELD_DEFAULT_RADIUS=96 // If I set this to 95 or 97 or anything not divisible by 12, it will break. Can someone explain me what these distancefield environment variables do and whether this is an intended behavior?

@SGaist I decided to go that route and have it build based upon platform: versiondata.target = buildinfo.h unix:versiondata.commands = $$PWD/create_buildinfo versiondata.depends = FORCE QMAKE_EXTRA_TARGETS += versiondata PRE_TARGETDEPS += buildinfo.h I have a command called create_buildinfo that makes buildinfo.h. To add platforms I just add win32: or whatever and create different commands.

Hi and welcome to devnet, Can you provide a minimal compilable example that shows that behaviour ?

Hi, That's a question you should ask on the bug report directly.

Like said @SGaist, that's just a silly question. @SGaist said in Slot called two times for one signal: Might be a silly question but are you sure that your method setting connection is only called once ? I didn't pay attention to the methods that are called in the addNewTab() method. Indeed, setUpTabConnexions() is called twice at some point. After using qDebug() and breakpoints, and I was able to find the cause of this problem. Sorry to have bothered you!

@JonB said in Any special requirements in a module to debug?: GDB will debug both the parent and the child process. This is going to be just very confusing, if you ask me ... I'd rather keep only one victim on a fork.

If you need to store a QModelIndex then use QPersistentModelIndex instead, that way changes to the model ordering/indices is going to be propagated. You should never keep an ordinary model index outside the current scope (i.e. stack frame). The point is that the model may (want to) reorder itself and your regular model index is going to just point to nirvana in this case.

@GrafZ4hl said in SIGSEV on ~QColorSpace Destructor: connect (this->Taktgeber, &QTimer::timeout, this, &C_frm_Camera_Calibration::Taktgeber_Tick); What is this? if(this->Main->cameraManager->pipelineQue->try_pop(pData)) What is pData? What is pipelineQue? What's the implementation of try_pop? I'd hazard that your pData's containing garbage or doesn't live long enough for whatever it is you're trying to do.

I simply don't understand what your code tries to do - you create a QGraphicsScene but don't use it, you overwrite paintEvent() but don't paint anything in there so your widget can't display anything. You create a QGraphicsView inside a widget but show it as standalone widget - it's just confusing. btw: QGpraphicsObject has a rotation property.

@feistykittykat said in Using Qt 5.12, glDrawBuffer is not found in QOpenGLExtraFunctions, shouldn't this be supported?: Just call it directly in Qt without using OpenGLFunctions or a derived class? No, I gave you the link to the Qt function...

@SGaist good thanks

@JonB , doh!, Perfect, thank you, completely overlooked that one!

@Adso4 For https, what have you done about installing SSL libraries? You need them.

From the QGraphicsItem docs: "The mouse press event decides which item should become the mouse grabber (see QGraphicsScene::mouseGrabberItem()). If you do not reimplement this function, the press event will propagate to any topmost item beneath this item, and no other mouse events will be delivered to this item." So there is something fishy going on for sure... EDIT: Also, I use items which cover other items all the time. I don't typically have issues what items "catch" the events, unless I have event handlers in there. However, consider that certain GraphicsItemFlags can implicitly cause items to accept mouse events (e.g. if the item is moveable, it needs to handle mouse clicks).