The "proper" way to do this is to check your hardware state in the model tick() function, and if it changes, call a virtual modelListener function. Any screen you want to respond to the button press should implement this function in its presenter. When the presenter method is called, get the data from the model and call an appropriate method on the view.
For example, let's say you want to turn a box a certain color if the button is pressed.
In Model.cpp:
bool buttonStatus = false; // this should be a private variable in Model.hpp, with a public accessor like getButtonStatus();
void Model::tick(){
bool currentButtonStatus = checkButtonHardware(); // implement this on your own
if(currentButtonStatus != buttonStatus){
buttonStatus = currentButtonStatus;
modelListener->buttonChanged();
}
}
In ModelListener.hpp:
virtual void buttonChanged() {}
In Screen1Presenter.cpp: (of course create prototypes in .hpp)
void Screen1Presenter::buttonChanged(){
if(model->getButtonStatus() == true){
view.setBoxColor(BoxColorEnum::BLUE);
} else {
view.setBoxColor(BoxColorEnum::RED);
}
}
Finally, in Screen1View.cpp (of course create prototypes in .hpp)
enum class BoxColorEnum{ RED, BLUE, ... }; // in hpp file
#include <touchgfx/Color.hpp>
void Screen1View::setBoxColor(BoxColorEnum color){
switch(color){
case BoxColorEnum::RED:
box1.setColor(touchgfx::Color::getColorFrom24BitRGB(255, 0, 0);
break;
//... and so on
}
box1.invalidate();
}
Your checkButtonHardware button can either check it directly (e.g. HAL_GPIO_ReadPin(GPIOx, GPIO_Pin)) or it can receive an event from the RTOS if your hardware is processed in another task. The important thing is that your state is stored in the model, the modelListener is informed of changes, interested presenters decide what view functions to call depending on the model state, and the view is only concerned with changing the visuals.
Beyond this, if setting a variable with the state of a hardware pin is already outside your knowledge, the TouchGFX forum is not the place to ask those questions. TouchGFX is a graphics framework only. Just because you can put UIs on discovery boards without much fiddling, it doesn't mean that all the work is done for you. You are responsible for implementing your own hardware routines, and more basic STM32 tutorials are where you could acquire this knowledge.
Disclaimer: code should be used as a reference only, I've not validated or compiled it.
