Here is where I have found the chain to fail. In this test program I wrote, the first screen updates perfectly in the model tick function, shown below. The second screen's files have been set up identically to the first one's, with only the update function name being changed. Maybe I misunderstand naming or calling convention, but you can see from this snippet what I am doing. Again, the first bit of code to process message queue 1 works, but the second one processing message queue 2 does not:
void Model::tick()
{
unsigned int counter;
//if a new message has arrived in the queue from somewhere (in this case, the
//periodic update task in main()), trigger the start of a screen update
if(xQueueReceive(messageQS1, &counter, 0) == pdTRUE){
//send the data received in the queue on to be processed
//and ultimately passed to the View 1 screen for displaying
modelListener->setNewCounter1Value(counter);
}
if(xQueueReceive(messageQS2, &counter, 0) == pdTRUE){
//send the data received in the queue on to be processed
//and ultimately passed to the View 2 screen for displaying
modelListener->setNewCounter2Value(counter);
}
}
And, here is the code for the model listener, showing the virtual functions:
class ModelListener
{
public:
ModelListener() : model(0) {}
virtual ~ModelListener() {}
void bind(Model* m)
{
model = m;
}
virtual void setNewCounter1Value(unsigned int){}
virtual void setNewCounter2Value(unsigned int){}
protected:
Model* model;
};
