Feature Request: Persist Edited CAN Input Names & Support Hex CAN IDs

[ykcab]

1. Persist Edited CAN Input Names

Description
When a CAN input name is edited, the updated name should be saved to the database and reflected consistently across the entire application.

Current Behavior
If I rename a CAN input (e.g., CANin1 → KEY_IGN_STATE), the updated name does not appear everywhere it should.

Expected Behavior

• The edited name must be saved in the database.
• The updated name must populate exactly as edited in all relevant locations.
• For example:
  • If CANin1 is renamed to KEY_IGN_STATE,
  • Then KEY_IGN_STATE should appear in the Output → Variable dropdown list and anywhere else that references this input.

Why This Is Important
This ensures consistency, avoids confusion, and prevents configuration errors caused by mismatched or outdated variable names.

2. Support Hexadecimal CAN IDs (Universal Setting)

Description
Add support for hexadecimal CAN IDs in the configuration.

Requirements

• Allow users to choose whether CAN IDs are represented in:

  • Hexadecimal (HEX), or
  • Decimal (DEC).

• The selection must be global/universal for the project or configuration.

• Mixing HEX and DEC formats in the same configuration should not be allowed.

Expected Behavior

• A clear setting (e.g., dropdown or toggle) to select ID format: HEX or DEC.
• All CAN IDs in the system follow the selected format consistently.

Why This Is Important

• Many CAN tools and documentation use hexadecimal format.
• A universal format setting prevents ambiguity and configuration mistakes.