TDDefs.h

Clone Tools
  • last updated a few seconds ago
Constraints
Constraints: committers
 
Constraints: files
Constraints: dates
Does OperationModes.c need to include TxParams.h? TxParams is not a mode.

Does OperationModes.c need to include TxParams.h? TxParams is not a mode.

I think we should initialize pre-treatment mode here now that we have a pre-treatment mode.

I think we should initialize pre-treatment mode here now that we have a pre-treatment mode.

Should we request pre-treatment mode here instead? How do we get to pre-treatment mode?

Should we request pre-treatment mode here instead? How do we get to pre-treatment mode?

Yes, I deleted.

Yes, I deleted.

Deleted.

Deleted.

Removed

Removed

Deleted.

Deleted.

Done

Done

Remove extra blank line.

Remove extra blank line.

MODE_TPAR should be deleted.

MODE_TPAR should be deleted.

It should no longer be called from OperationModes.c because we are deleted the TxParams mode (delete from enum and any switch statements in OperationModes.c).

It should no longer be called from OperationModes.c because we are deleted the TxParams mode (delete from enum and any switch statements in OperationModes.c).

ModeTxParams.c/.h are still not deleted. I want you to delete them and commit/push that change. Then I will see both files in RED here in this CR.

ModeTxParams.c/.h are still not deleted. I want you to delete them and commit/push that change. Then I will see both files in RED here in this CR.

Thanks for the clarification. This handler already follows the single-parameter MESSAGE_T *message pattern, and the message ID is already defined and registered in Messaging.c. I’ll keep using the ...

Thanks for the clarification. This handler already follows the single-parameter MESSAGE_T *message pattern, and the message ID is already defined and registered in Messaging.c. I’ll keep using the existing ID, ensure payload length is validated, and parse the param/value from the payload as expected.

Yes, this is called in OperationModes.c

Yes, this is called in OperationModes.c

Sure.

Sure.

Added.

Added.

Added.

Added.

Not sure how Doxygen will handle this comment between the /// and the const. I think we should remove it.

Not sure how Doxygen will handle this comment between the /// and the const. I think we should remove it.

Done

Done

move static function after public function

move static function after public function

let public function on top

let public function on top

Let all public functions come on top for all files

Let all public functions come on top for all files

I didn't see this in header file.

I didn't see this in header file.

I don't see these Lower/Upper Range Limit functions declared in the header file.

I don't see these Lower/Upper Range Limit functions declared in the header file.

Need to delete this unit (ModeTxParams.c/.h). Also need to remove the mode from the modes enumeration and from OperationModes.c.

Need to delete this unit (ModeTxParams.c/.h). Also need to remove the mode from the modes enumeration and from OperationModes.c.

I don't think we need this signal function since this is not a mode anymore. Is this function being called somewhere?

I don't think we need this signal function since this is not a mode anymore. Is this function being called somewhere?

Added

Added

Added

Added

Updated

Updated

I don't see an isTreatmentParamInRange function. I think we need to copy from the ModeTxParams.c.

I don't see an isTreatmentParamInRange function. I think we need to copy from the ModeTxParams.c.