3rd Party Software

@trin94 Thanks for getting back to me and for all your help

@LTartarini I used the same example zip file and only had to tweak a little bit to make it run on Qt 5.15.2.

First they split up QObject::setEventFilter into setEventFilter and setNativeEventFilter. We need the latter one. This requires making the Mouse3DInput class a subclass of QAbstractNativeEventFilter

class Mouse3DInput : public QObject, public QAbstractNativeEventFilter { ... }

Now we have to move the implementation of the original bool Mouse3DInput::RawInputEventFilter(void* msg, long* result) function into the definition of the QAbstractNativeEventFilter::nativeEventFilter(const QByteArray &eventType, void *message, qintptr *result) override.

class Mouse3DInput : public QObject, public QAbstractNativeEventFilter { Q_OBJECT public: Mouse3DInput(QWidget* widget); ~Mouse3DInput(); //we have to make it non static and public to match the virtual function bool nativeEventFilter(const QByteArray &eventType, void *message, long *result) override; ... } //Mouse3DInput.cpp bool Mouse3DInput::nativeEventFilter(const QByteArray &eventType, void *message, long *result) { if (gMouseInput == 0) return false; MSG* msg = (MSG*)(message); if (msg->message == WM_INPUT) { HRAWINPUT hRawInput = reinterpret_cast<HRAWINPUT>(msg->lParam); gMouseInput->OnRawInput(RIM_INPUT,hRawInput); if (result != 0) result = 0; return true; } return false; }

In the constructor we can use our new filter.

Mouse3DInput::Mouse3DInput(QWidget* widget) : QObject(widget) { fLast3dmouseInputTime = 0; InitializeRawInput((HWND)widget->winId()); gMouseInput = this; qApp->installNativeEventFilter(this); }

@mtrch
Agree with you, I say because I did practice what you mentioned here.
Yes, it is workable.
Best regards,
Thuan T. Nguyen

Ok finally builded, thanks for help :)

@hzha said in disposition qxmpp:

didn't work

In what way it didn't work?
Saying "didn't work" does not help much.

Please show your CMakeLists.txt. You are not linking against the Qt library.

@Christian-Ehrlicher

If you look at qwt oscilloscope example the curve data is updated in another thread than GUI.
I do the same. I update only the curve data and guard it with mutexes. In replot the data is locked. But I guess this must be the reason so I'll try to come up with a small compilable example to show the error.

@mtalha2621 My bad, I misread the error messages. What I had in mind when answering is for you to use your custom pipeline with OpenCV.

@Christian-Ehrlicher

Yeah, this seemed to be the problem...
Took much longer to than I want to admit before I found it...

I wanted to post my fix already, but newbies on the forum can only post every 10 minutes 😅

Hi,

Please provide a minimal compilable example that shows the situation.

Hi,

Did you check the BACnet developer aids ? There's a list there of implementation for different languages including C.

Hi and welcome to devnet,

Did you build that software yourself ?
Where did you get the sources from ?
Which version of Qt are you using ?
How did you install it ?

@jsulm @Christian-Ehrlicher

Well, my code doesn't work after but I'll figure it out later.

I can say that the linking works properly now. Thanks for your help guys!

According to Qt documentation you can integrate your qml in UE:
https://doc-snapshots.qt.io/qt6-dev/qquickgraphicsconfiguration.html#configuration-for-external-rendering-engines-or-xr-apis

@horizonQt
i fixed it. look at qwt-6.1.6/playground/curvetracker . I hope it helps

@jsulm
https://microseismic.cn/use-qwt-library-in-qt-to-display-seismic-waveforms.html ı follow this and ı solved thanks

@SGaist ı solved thanks

@Cedric-air
No, that shows it is not optional, it shows that you should not be trying to alter itemInfo in the signal/slot. But your commented out/erroneous code was trying to set that visible.

@Chs_QtLearner Please check config.log file to see why Open62541 security was disable (most probably some lib is missing).