ui_build_history.log

Clone Tools
  • last updated a few minutes ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
UI Staging Unreviewed Commits
UI Staging Unreviewed Commits
RESOLVED.

RESOLVED.

Since we have more than one message which is using the dynamic structure now we have a "MAbstractDynamic" model (link bellow) as the parent and these codes have been moved to the parent and all the...

Since we have more than one message which is using the dynamic structure now we have a "MAbstractDynamic" model (link bellow) as the parent and these codes have been moved to the parent and all the 3 messages are using the same structure.
http://dvm-linux02:8060/cru/#UI-DEN-10424-1CFR-27600

Where was this code moved to or was it dead code laying around?

Where was this code moved to or was it dead code laying around?

UI-DEN-10424_FW Request A4 A5 Msg Log
UI-DEN-10424_FW Request A4 A5 Msg Log
RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.

Updated.

Updated.

Added.

Added.

Added.

Added.

Added.

Added.

Added.

Added.

It has been removed. We should reserve our Alarm System mostly for critical HW issues during treatment.

It has been removed.
We should reserve our Alarm System mostly for critical HW issues during treatment.

RESOLVED.

RESOLVED.

I mean, all others appear to be in the following order: 1) number of params and 2) size of params. So to be consistent, shouldn't this be 1 * 15 (1 param, 15 bytes)?

I mean, all others appear to be in the following order: 1) number of params and 2) size of params.
So to be consistent, shouldn't this be 1 * 15 (1 param, 15 bytes)?

RESOLVED.

RESOLVED.

RESOLVED.

RESOLVED.