e tcm/event order

Hello,

I have the following issue:
I have two event, one is generated from an hdl signal (signal_r) and the other is emitted from a tcm (test_e). I have another tcm, which is waiting from both event, and after when is occurred it do something depending on the occurred event. The problem is that, this two event can happen in the same clock cycle, and in that case the emitted event (test_e) has "higher" priority (I mean here, that if both event occurs in the same cycle, only action fo the emitted event should be executed).

The issue is that, when the two events occurs in the same cycle, the event from the HDL signal is emitted first, and the tcm executes the action associated with this event, and the action associated with the other event is not executed. But my expectation is that, only the action associated with the second event should be executed. This is because the tcm which is emitting the second event runs only after the other tcm which is waiting for the events. My question is that, is there any way to modify the tmc’s execution order to avoid this problem.

I hope I was understandable. I wrote a sample code to explain my problem:

extend sys {
    sig_clock : in simple_port of bit is instance;
        keep sig_clock.hdl_path() == "clk";

    sig_signal : inout simple_port of bit is instance;
        keep sig_signal.hdl_path() == "signal";       

    event clk is rise(sig_clock$) @sim;
   
    event signal_r is rise(sig_signal$) @clk;
    on signal_r { message(LOW, "signal_r");};
   
    event test_e;
    on test_e { message(LOW, "test_e");};

    flag : bool;
        keep not flag;
   
   
    tcm_1() @clk is {
        while (TRUE) {
            wait (@signal_r or @test_e);
           
            if (now @test_e) {
                message(LOW, "flag true");
            } else if (now @signal_r) {
                message(LOW, "signal 1");
            };
           
        };       
    };

    tcm_2() @clk is {
        wait [5];

        flag = TRUE;
               
        emit test_e;
    };
   
   
    tcm_3() @clk is {
        wait [50];
       
        stop_run();
    };   

    run() is also {
        start tcm_1();
        start tcm_2();
        start tcm_3();           
    };  
};

The signal_r event is emitted in the same cycle as the test_e. The problem is that, the printed message is "signal 1" instead of "flag true".