With dialect 16 we have added full buffering to the OBLCD on the MMi201 (though not the MS12). That means that when your program displays something, the display data is written instantly to a dedicated memory area (which happens very quickly) and is then transferred to the actual LCD device “at leisure”. That way your program is not held up while the relatively slow transfer of data to the LCD takes place.

There are still a couple of things you have to watch out for when using the OBLCD in MultiTrack:

1. If a task yields between setting the cursor (OBLCD_SetCur) and displaying something, another task might move the cursor in the meantime and scramble the display. The best policy therefore is to set the cursor and display the data without allowing an intervening yielding instruction.
2. Displaying numbers, especially floating point numbers, takes quite a bit of of processor time. If you update number displays very frequently you will slow down the whole program.