Hi Professional,
If you create a simple designer project with a button and an interaction that reacts to that button, you'll see what i mean. Here's the code the designer generates - I've posted parts of the baseview cpp and hpp file. You'll see that :
- the buttonCallback is defined in the view base constructor. Here, the callback is tied to a handler method called buttonCallbackHandler() which is defined further down.
- The callback is templated with the recipient of the callback as well as a reference to the object responsible for the callback. And the handler takes just the responsible object reference.
- Once you set the action on the button, clicking it (due to button internals) should result in the handler method getting called.
I'm not sure if this helps clarify the process.
Screen1ViewBase::Screen1ViewBase() :
buttonCallback(this, &Screen1ViewBase::buttonCallbackHandler)
{
box1.setPosition(0, 0, 800, 480);
box1.setColor(touchgfx::Color::getColorFrom24BitRGB(255, 24, 24));
button1.setXY(246, 154);
button1.setBitmaps(Bitmap(BITMAP_BLUE_BUTTONS_ROUND_EDGE_SMALL_ID), Bitmap(BITMAP_BLUE_BUTTONS_ROUND_EDGE_SMALL_PRESSED_ID));
button1.setAction(buttonCallback);
add(box1);
add(button1);
}
void Screen1ViewBase::setupScreen()
{
}
void Screen1ViewBase::buttonCallbackHandler(const touchgfx::AbstractButton& src)
{
if (&src == &button1)
{
//Do something based on button 1 clicked
}
}
...
private:
/*
* Callback Handler Declarations
*/
void buttonCallbackHandler(const touchgfx::AbstractButton& src);
/*
* Callback Declarations
*/
touchgfx::Callback<Screen1ViewBase, const touchgfx::AbstractButton&> buttonCallback;
};
#endif // SCREEN1_VIEW_BASE_HPP
