MDRMux will not be highlighted unless MDRCk is set and there is a valid data flow through the MDRMux.
This is in contrast to the CMux, which will color itself and the C bus as long as there is valid data leaving CMux, even if that data is not clocked in to a register.
For consistency with the rest of the Pep9CPU application, all MDR multiplexers should be highlighted if data is flowing through them, even if the data value will not be clocked. More generally, every multiplexer in the application should have this behavior.
This bug inconsistency is also present in the two-byte model with MDREMux, MDROMux.
MDRMux will not be highlighted unless MDRCk is set and there is a valid data flow through the MDRMux.
This is in contrast to the CMux, which will color itself and the C bus as long as there is valid data leaving CMux, even if that data is not clocked in to a register.
For consistency with the rest of the Pep9CPU application, all MDR multiplexers should be highlighted if data is flowing through them, even if the data value will not be clocked. More generally, every multiplexer in the application should have this behavior.
This bug inconsistency is also present in the two-byte model with MDREMux, MDROMux.