Remove blank line.

If this is a override message handler, it is not in the table in Messaging.c and it does not have the proper parameter list (1 parameter for a message pointer).

Can we have a payload structure (packed to 1 byte alignment) with 1 field of type U08 for this message and then replace '1' with 'sizeof( new struct type )' ?

Add blank line between declarations and rest of function code (throughout this unit)

Add blank line before return statement. ( throughout this unit )

Add blank line before return statement.

Add blank line between declarations and rest of function code.

Add blank line between declarations and rest of function code.

Add blank line between declarations and rest of function code.

Add blank line between declarations and rest of function code.

Add blank line before return statement.

Add blank line between declarations and rest of function code.

Add blank line before return statement.

Add blank line before return statement.

Add blank line before return statement.

Indent too deep here.

Remove blank line.

Indent looks too deep here.

1 blank line here is sufficient.

Remove blank line.

Remove blank line.

Remove blank line.

Add a blank line after private defs banner.

Remove extra blank line.

Remove blank line.

Just 1 blank line here is sufficient.

Since these are coming from UI s/w now (right?), I don't think they should begin with "test" which we reserve for messages that only come from Dialin.
Move up above "test" functions.

This is a common unit - could be built into DD or TD f/w. Need #ifdef to see if _DD_ or _TD_ build so you know which messaging and records to initialize.

These don't look like UI alarms. Comment suggests we already know what to call these. Why aren't we just using the names we want?

Make sure Dialin gets these too when you merge.