Dana Good

thank you, Miro! This is exactly what I needed.

Hi Miro, I frequently run into the question of which calls against a QTimeEvt will assert in the wrong timer context, and which calls can be made at any time. I see from the above that disarm() can be called at any time, but it is cumbersome to look through support messages each time a question comes up on one or another of the QTimeEvt calls.. I'm wondering if I've missed a location in the documentation where each of these are laid out, and if not, if that could be added. I make extensive use of...

QM reports the return value from QActive_recall() as a QEvt const *. It is defined in the header file as returning a bool. The extended documentation in QM reports: "QActive_recall() returns the pointer to the recalled event to the caller. The function returns NULL if no event has been recalled." My versions may be out of date, so this may already be fixed. I'm using QM version 5.1.0, and the header file is qf.h, "Last updated for version 6.8.0"

I have two branches of concurrent development on my QM model. I merged the smaller branch first, hoping to minimize merge conflicts. I have merge conflicts in my model that I am uncertain how to resolve. Unfortunately, there are significant changes in the second branch, so simply lining these up and going through the differences change by change would involve hundreds of small investigations. I'm willing to make appropriate changes using the QM tool How can I understand what I am seeing in these...

I have two branches of concurrent development on my QM model. I merged the smaller branch first, hoping to minimize merge conflicts. I have merge conflicts in my model that I am uncertain how to resolve. Unfortunately, there are significant changes in the second branch, so simply lining these up and going through the differences change by change would involve hundreds of small investigations. I'm willing to make appropriate changes using the QM tool How can I understand what I am seeing in these...

I have two branches of concurrent development on my QM model. I merged the smaller branch first, hoping to minimize merge conflicts. I have merge conflicts in my model that I am uncertain how to resolve. Unfortunately, there are significant changes in the second branch, so simply lining these up and going through the differences change by change would involve hundreds of small investigations. I'm willing to make appropriate changes using the QM tool How can I understand what I am seeing in these...

I have two branches of concurrent development on my QM model. I merged the smaller branch first, hoping to minimize merge conflicts. I have merge conflicts in my model that I am uncertain how to resolve. Unfortunately, there are significant changes in the second branch, so simply lining these up and going through the differences change by change would involve hundreds of small investigations. I'm willing to make appropriate changes using the QM tool How can I understand what I am seeing in these...

I have two branches of concurrent development on my QM model. I merged the smaller branch first, hoping to minimize merge conflicts. I have merge conflicts in my model that I am uncertain how to resolve. Unfortunately, there are significant changes in the second branch, so simply lining these up and going through the differences change by change would involve hundreds of small investigations. I'm willing to make appropriate changes using the QM tool How can I understand what I am seeing in these...