determine which button was pressed on a screen

[FJB2069]

I have two buttons on Screen1.  Both interactions change screen to Screen2.  

Can I determine which button was pressed when in Screen2View::setup?

Or do I need to use a separate virtual functions and then create a variable setting the button called?

 

[Marc_LM]

Go create a widget or a screen with many flex buttons.
In the base class you will see how the source of the button are detected.

void *::flexButtonCallbackHandler(const touchgfx::AbstractButtonContainer& src)

 

[FJB2069]

I see the flexButtonCallback in Screen1ViewBase.cpp.

I am trying to break on this section to follow when I press button, but only breaks when I return to screen, not button press.

Sorry, I am not familiar with how to use this callback or handler, any help would be appreciated!

 

[FJB2069]

wait, I see in the handler it shows each button.....  I will try to make a variable that saves which button was pressed so that after the data is input in screen2 I can return the data the correct flexbutton text area.

 

[FJB2069]

How can I save which button was pressed in the Model before the screen is changed?

In the base view it shows which button was pressed, but how can I save that button into a variable using MVP ( I assume this would be the correct way) before the screen is changed.  then be able to access that variable when I return to screen 1?

void Screen1ViewBase::flexButtonCallbackHandler(const touchgfx::AbstractButtonContainer& src)
{
 if (&src== &flexButtonNum10s)
 {
 //Interaction1
 //When flexButtonNum10s clicked change screen to Screen2
 //Go to Screen2 with no screen transition
 application().gotoScreen2ScreenNoTransition();
 }
 if (&src== &flexButtonNum1s)
 {
 //Interaction2
 //When flexButtonNum1s clicked change screen to Screen2
 //Go to Screen2 with no screen transition
 application().gotoScreen2ScreenNoTransition();
 }
}

 

[GaetanGodart]

Hello @FJB2069 ,

 

Regarding your last message, it look like you have created 2 interactions :

• one with button 10 as the trigger and the action is go to screen 2
• one with button 1 as the trigger and the action is go to screen 2

This creates functions in the base file that cannot be modified by hand.

So instead, you could modify your 2 interactions so that the action is either "call new virtual function" or create an action (with a value of type int8) and call that action while specifying the button number. Then, on those 2 interactions, select "can trigger another interaction" and create 2 new interactions where the trigger is "another interaction is finished" and the action is to change to screen 2.

This way, you are able to call extra code (through the virtual function or through the action) before the screen changes.

 

Regards,

[FJB2069]

Are you referring to creating a custom container with an action1 and then creating an interaction action1 is called int8_t?  then creating an action to change screen or a virtual function, then trigger another action......  I getting confused just writing this!

 

I understand the concept, but not sure how to implement it.  Can you be more specific or is there a tutorial on this?