Re: [Hamlib-developer] Feature request: User friendly version of errors

[Peter M. <pet...@gm...>]

Thanks George. You are very kind.

For some reason it has taken me a while to figure out that the SourceForge project is no longer the active one.

I’ll raise a ticket asking that rigerror2 be added to the API reference

73,

Peter
VK3TPM.

> On 2 Sep 2025, at 10:25 am, George Baltz <geo...@gm...> wrote:
> 
> Forgot to answer your other comment - the ticketing system(and other admin stuff) was moved from sourceforge to github.com -
> 
> https://github.com/Hamlib/Hamlib
> 
> 73, n3gb
> 
> On 8/31/25 5:58 PM, Peter Marks wrote:
>> Dear Hamlib developers,
>> 
>> I don’t seem to be able to create a feature request ticket on sourceforge. The button is dim.
>> 
>> When hamlib reports an error, typically a timeout talking to the radio, the error string returned by rigerror() is very detailed and includes a stack trace.
>> 
>> const char* rigerror <https://hamlib.sourceforge.net/manuals/1.2.15/group__rig.html#ga675d0903517323b2689446d9513fc8db>	(	int 	errnum	)	
>> get string describing the error code
>> 
>> 
>> I’m involved in the FreeDV <https://freedv.org/> project which uses hamlib. We show the error string and find that it is intimidating to users. They sometimes report that FreeDV has “crashed”.
>> 
>> It would be great if there was a second version of the error string with just the bit that the user needs. “Timeout talking to rig” for example.
>> 
>> Many thanks for your great work.
>> 
>> Peter
>> VK3TPM
>> 
>> 
>> 
>> _______________________________________________
>> Hamlib-developer mailing list
>> Ham...@li... <mailto:Ham...@li...>
>> https://lists.sourceforge.net/lists/listinfo/hamlib-developer
> _______________________________________________
> Hamlib-developer mailing list
> Ham...@li...
> https://lists.sourceforge.net/lists/listinfo/hamlib-developer