Re: [Interest] [QtSerialBus] [CAN] Blocking API planned?

2016-04-11 Thread André Hartmann
, 2016 09:13 To: Interest@qt-project.org Subject: [Interest] [QtSerialBus] [CAN] Blocking API planned? Hi all, right now the CAN bus API provides the signals framesReceived() and framesWritten(). For some cases, it's easier to have a thread that blocks until an event occurs. Therefore, the addition

Re: [Interest] [QtSerialBus] [CAN] Blocking API planned?

2016-04-11 Thread Blasche Alexander
@qt-project.org> on behalf of André Hartmann <andre.hartm...@iseg-hv.de> Sent: Monday, April 11, 2016 09:13 To: Interest@qt-project.org Subject: [Interest] [QtSerialBus] [CAN] Blocking API planned? Hi all, right now the CAN bus API provides the signals framesReceived() and framesWritten(

[Interest] [QtSerialBus] [CAN] Blocking API planned?

2016-04-11 Thread André Hartmann
Hi all, right now the CAN bus API provides the signals framesReceived() and framesWritten(). For some cases, it's easier to have a thread that blocks until an event occurs. Therefore, the additional functions bool waitForFramesReceived(int msecs) bool