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
I'm trying to support more than just the latest version of hamlib which requires knowing which bugs are present in the used version and need workarounds. A common way of doing this is to compare the library-provide version number against a list of workarounds.
Maybe I missed it, but I didn't see anything like that in rig.h. Could you add these or something like them to allow for easy integer comparisons?
With these, I can then conditionally disable some functionality. E.g., KX2 power calculation doesn't work prior to 4.5.5 (I'm assuming the next version will be 4.5.5) or netrigctl prior to 4.3.1 may segfault in power2mW.
I realize that it won't help with already released versions, but it'd help with usage of future hamlib versions.
Note that hamlib_version contains "Hamlib 4.4" and therefore doesn't have enough granularity. (Also, parsing such a string in C is a headache compared to something like the #defines above.)
Thanks for taking a look.
The text was updated successfully, but these errors were encountered:
I'm trying to support more than just the latest version of hamlib which requires knowing which bugs are present in the used version and need workarounds. A common way of doing this is to compare the library-provide version number against a list of workarounds.
Something like this should do:
Maybe I missed it, but I didn't see anything like that in rig.h. Could you add these or something like them to allow for easy integer comparisons?
With these, I can then conditionally disable some functionality. E.g., KX2 power calculation doesn't work prior to 4.5.5 (I'm assuming the next version will be 4.5.5) or netrigctl prior to 4.3.1 may segfault in power2mW.
I realize that it won't help with already released versions, but it'd help with usage of future hamlib versions.
Note that hamlib_version contains "Hamlib 4.4" and therefore doesn't have enough granularity. (Also, parsing such a string in C is a headache compared to something like the #defines above.)
Thanks for taking a look.
The text was updated successfully, but these errors were encountered: