libQCR issueshttps://jugit.fz-juelich.de/mlz/libqcr/-/issues2024-01-22T11:06:33+01:00https://jugit.fz-juelich.de/mlz/libqcr/-/issues/6Missing GUI element: Boolean state indicator2024-01-22T11:06:33+01:00Christian TrageserMissing GUI element: Boolean state indicatorLibqcr is missing an GUI element which shows an boolean state (without the ability of chaning it by the user).
As far as I know most often these functionality has been implemented by using an read-only checkbox element. But libqcr should...Libqcr is missing an GUI element which shows an boolean state (without the ability of chaning it by the user).
As far as I know most often these functionality has been implemented by using an read-only checkbox element. But libqcr should have its own element.https://jugit.fz-juelich.de/mlz/libqcr/-/issues/9Linking Issues when gLogger is connected via QObject::connect under windows2024-02-14T13:44:48+01:00Christian TrageserLinking Issues when gLogger is connected via QObject::connect under windowsThis has been first seen with this (now replaced) `utest/10_logger.cpp` TEST. The linking issues arise from `QObject::connect`. This seem to only occur under windows while under linux this works perfectly fine.
~~~
#include "QCR/engine/l...This has been first seen with this (now replaced) `utest/10_logger.cpp` TEST. The linking issues arise from `QObject::connect`. This seem to only occur under windows while under linux this works perfectly fine.
~~~
#include "QCR/engine/logger.h"
#include "catch.hpp"
TEST_CASE("QcrLogger", "[signal]")
{
gLogger = new QcrLogger("10.log");
QString lastReceived;
QObject::connect(gLogger, &QcrLogger::sigLine, [&lastReceived](const QString& received) {
lastReceived = received;
});
gLogger->log("bla1");
CHECK(lastReceived == "bla1");
}
~~~
This issue can be reproduced. For example in `demo/demo1_triggerbutton.cpp`. If a connection with a signal is inserted in this file then the same linking errors appear.