You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It sounded like a great idea in the beginning but the actual benefit is rather neglectable. Anyone using this software is going to use only the APIs anyways. It isn't beneficial at all to have the parameters generated as constants.
I want to embed the params.csv, enums.csv and devices.csv (does not exist) in the binary similar to the default config and provide commands to export them. This would also enable switching between parameter definitions in order to support older ROTEX HPSUs.
This should even make the implementation a bit simpler as well.
The text was updated successfully, but these errors were encountered:
It sounded like a great idea in the beginning but the actual benefit is rather neglectable. Anyone using this software is going to use only the APIs anyways. It isn't beneficial at all to have the parameters generated as constants.
I want to embed the
params.csv
,enums.csv
anddevices.csv
(does not exist) in the binary similar to the default config and provide commands to export them. This would also enable switching between parameter definitions in order to support older ROTEX HPSUs.This should even make the implementation a bit simpler as well.
The text was updated successfully, but these errors were encountered: