Hi @Community member
Below some code. I simplified it and I used integer values instead of texts but the result is the same. Each method will only called once when updating ValueA and ValueB.
Model.cpp:
void Model::updateValueA(const uint32_t newValue)
{
m_valueA = newValue;
if (modelListener != 0)
{
modelListener->updateValueA(m_valueA);
}
}
void Model::updateValueB(const uint32_t newValue)
{
m_valueB = newValue;
if (modelListener != 0)
{
modelListener->updateValueB(m_valueB);
}
}
DevelopmentPresenter.cpp
void DevelopmentPresenter::updateValueA(const uint32_t newValue)
{
view.updateValueA(newValue);
}
void DevelopmentPresenter::updateValueB(const uint32_t newValue)
{
view.updateValueB(newValue);
}
DevelopmentView.cpp
void DevelopmentView::updateValueA(const uint32_t newValue)
{
Unicode::snprintf(txt_aBuffer, TXT_A_SIZE, "%d", newValue);
txt_a.invalidate();
}
void DevelopmentView::updateValueB(const uint32_t newValue)
{
Unicode::snprintf(txt_bBuffer, TXT_B_SIZE, "%d", newValue);
txt_b.invalidate();
}
In my opinion it is not wrong code for the screen, because the error happens on different screens and also with generated code (e.g. buttons -> old state will displayed).
I think TouchGFX use an outdated screenbuffer when updating a new value. We are using a HAL/DMA implementation which is adapted from the TouchGFX examples. I investigating this implementation but I did not found a difference until now. I also tried NoDMA instead of the DMA Implementation -> same result.
Any other ideas? I'm grateful for every hint.
Best regards
Marco
