RASP Eng export doesn't have validation.

[SparkRocketLab]

When I went to export a RASP Engine file, I ran into a validation issue with 2 of the fields.

It turns out the RASP Eng file format does not allow spaces to be in either the motor designation or name. However, RMTS will let you input spaces without issues. I see 2 ways to solve this problem:

1. Update PyFormGen to allow an optional validation function. This would enable custom validations for future issues and allow the user to fix the error how they see fit by displaying a validation message and canceling the save.
2. Escape spaces with a character like an underline in the engExportWidget okPressed function. This is easier but not as transparent to the user.

Let me know what way which way you to go and I'll post a PR.

[reilleya]

I like 1 better, but understand it is more to ask. Maybe we do 2 as a stopgap for now, and do 1 later? Unless you want to do 1 right away. Will get to your other PRs soon, just been a hectic couple of weeks for me!

[SparkRocketLab]

I like 1 better as well. I also think that fleshing out PyFormGen into a more functional form input library with unit conversion would unlock some functionality in more than just the RMTS software. I looked at the PyFormGen Repo and think I got a handle on how to do it. A few notes:

• PropertyCollection should probably be persisted through to the CollectionEditor. You can then use the PropertyCollection to hold custom validation functions, which is probably the proper spot for them.
• The base Property class will be able to assign a custom validation function. There will be a validation error variable for the property that can be set by the validation function. That variable allows the CollectionEditor to bubble it up through the UI on save.
• We can implement a validation warning in the collection edit. I'll check to see what Qt has standard for this.

Shouldn't take me too long.

[reilleya]

Sounds great to me!