Eike Stepper

Hi Mirko, All your comments make sense to me and I can not emphasize enough how much I appreciate your support! For my current mini project I'll give up on the submachine topic, but I'm really looking forward to an opportunity for trying out QP/C++. For example I'm curious whether submachines support an own set of instance variables. In the modeler I couldn't see anything to this extent. I have a final question, though. You advised me to change qpn_conf.h and increase the QF_MAX_TICK_RATE const....

No, there's not much duplication, but some. And I don't want to miss the opportunity to learn from the expert when and how best to use submachines ;-) This morning, for example, I noticed a bug in my previous Sunblind machine. The "automaticUp" state was missing an exit action that cancels the motor timer for the case that the state is exited through the inherited UP_PRESSED or DOWN_PRESSED transitions (and not through local timer expiration). Of course the very same bug had to be fixed in the (almost...

No, there's not much duplication, but some. And I don't want to miss the opportunity to learn the expert when and how best to use submachines ;-) This morning, for example, I noticed a bug in my previous Sunblind machine. The "automaticUp" state was missing an exit action that cancels the motor timer for the case that the state is exited through the inherited UP_PRESSED or DOWN_PRESSED transitions (and not through local timer expiration). Of course the very same bug had to be fixed in the (almost...

Oh btw., as an experienced Java software developer with a natural eye on design I wondered about the obvious symmetry between the "movingUp" and movingDown" substates in my new diagram. Intuitively I thought that submachines were a good match. But then I read that they don't support nested states. (A) Is that still true? (B) I know that nested states mostly exist to address the "transition explosion" problem. In my case, which of the two problems "transition explosion" or "duplication" would you...

Forgot to attach the new diagram...

Hi Miro (is that right?), Thank you very much for your prompt and exhaustive reply! I think I got all your valuable suggestions. Yesterday I already tried to (mis)use the "different tick rates" approach to achieve what I need, but for some reason it failed and I prematurely assumed that it's a wrong approach. Tomorrow I'll give it another shot. Your suggestion to make "LONG_PRESS" a distinct event in the first place is interesting, too. But I have other requirements regarding the sunblind control...

Hello, I've just started my very first home project with QP-nano. The goal is to let an Arduino react to four buttons in order to control two light bulbs (on/off/timed off) and a sunblind (up/down). So far I'm very impressed by QP-nano and the modeler. My model (diagram attached) has an AO "Light" and when the button is pressed and held it transitions to the substate "timed". In this substate a Q_TIMEOUT event is requested after one hour, which, on arrival transitions the light to "off". As you can...