change keyPressEvent log level

[micahwoodard]

Pull Request instructions:

• Please follow the update protocol
• Answer the questions below in detail. Your responses will be emailed to experimenters.
• If the experimenters must do anything new, provide detailed step by step instructions on the wiki
• If computer maintainers need to manually update anything, provide detailed step by step instructions
• Use markdown syntax in order for your comments to be rendered reliably in the email: "1." instead of "1)", use four spaces for indents.
• If you use the keyword "skip email" in the title, it will skip the email updates
• Merges from "develop" into "production_testing" should use the keyword "production merge" in the title for reliable indexing of updates
• Merges from "production_testing" into "main" should use the keyword "update main"

Describe changes:

• change log level from error to warning in keyPressEvent function to avoid creating issues when widgets have empty strings instead of floats

What issues or discussions does this update address?

• resolves Cannot convert input to float: lineEdit_init_stage_pos_x, '' #897

Describe the expected change in behavior from the perspective of the experimenter

• None

Describe any manual update steps for task computers

• None

Was this update tested in 446/447?

• 446/7

[alexpiet]

I support changing this to a warning so we don't generate tons of errors. However, we should still refactor the underlying code which is a mess. Up to @micahwoodard on the priority for that refactor

[XX-Yin]

I support changing this to a warning so we don't generate tons of errors. However, we should still refactor the underlying code which is a mess. Up to @micahwoodard on the priority for that refactor

Hey @alexpiet, I understand that the format check in the code is inherently complex, primarily due to the nature of the functions we aim to implement. If you have a better solution in mind, please feel free to share it and implement it!

[micahwoodard]

I think refactoring would work well with this issue. I will merge and close associated issues for now. It would be nice to clarify all the TP_ values and how they are being used to define the task performed. Maybe we can discuss in person