"*** Off the subject ***" At the time of testing application with SquishCoco, observed that Coco can't safely quit application and terminates the application and don't call the correct quit method of the application and that makes sense since the Squish Coco is another application and will immediately terminate the UI application and don't know how to properly quit the UI application. So UI application can't safely quit the threads. Therefore some threading features has been manually tested. The quitThread in each class is basically should name moveThread (move to main thread).
Thanks for this effort. If this and the other scripts are the implementations regarding the "SquishQt headless server" in the following link https://kb.froglogic.com/squish/howto/using-squish-headless-systems/ Please work with Dara Navaei to implement this on the server as well regarding the conversation Dara and I had a while ago and he is already aware of it.
Based on my review of the QObject classes underneath, the whole intent of the VIEW_DEF and VIEW_DEC macros is to provide a much more simplistic interfaces to the user when wanting to create views and their corresponding data. We also made the decision to not touch these two macros. Hence, my expectation is for all features implemented moving forward to follow this design pattern.
Note: If someone wants to look at the definition of these macros, they can always go back to their corresponding *.h.
Definitions: m is used for model data (structure) variables
Moving forward, my expectation is for all of us to follow the same naming convention. I have also requested BehrouzN to update the C++ Coding Standards.
Each reject reason (or none if no rejection) corresponds to a treatment parameter. Since there was no need to duplicate the lines for each parameter, I've now updated it so they are generated using list comprehension instead. Also I added the docstrings that were missing.
Since added one more parameter ( one F32, 4 bytes) in the payload of each messages the length should reflect the exact amount of the bytes and it needs to be changed to 8 * 4 for both of the : Gui::GuiActionType::ID_BloodFlow , Gui::GuiActionType::ID_DialysateInletFlow otherwise ui will read only 7*4 bytes and you will get zero for the last parameter (signal strength).
