While keyer is open, <CR> in RX(RST) field crashes Xlog

[HA5OB]

Binary package hint: xlog

While keyer is open, <CR> in RX(RST) field crashes Xlog

------------------------------------------------------------------------------------------------
** (xlog:8177): WARNING **: Widget not found: f134896151entry

(xlog:8177): Gtk-CRITICAL **: gtk_editable_get_chars: assertion `GTK_IS_EDITABLE (editable)' failed

------------------------------------------------------------------------------------------------

73 , Zoli

[John Nogatch (jnogatch)]

It appears that someone started modifying xlog's GUI, changing the naming convention, but that these changes were not propagated into the "Keyer" window, which is what is used in contest mode.

1. The reported problem was that hitting \r in the RX(RST) field of the main window, while keyer window is active, caused a crash. It was trying to pass a string to a callback which expected an int. I suspect that it was originally a string, & had been changed to int, but 2 places had been missed. Changing it back to string avoids the problem.

2. gtk error messages were appearing. Again, it appears that the name of a menu item had been changed from "Add" to "Write", but the keyer interface had not been updated to use the new name.

3. Entering a callsign, \r, fills in the RST fields, & hitting another \r failed to log the contact. Sending "clicked" to the "/ToolBar/Write" widget was not working, but did not cause an error message. Changing it to send "activate" to "/MainMenu/Edit/Write" allows the QSO to be logged correctly. I see many other places where "clicked" is used, but I do not know whether they are correct or not.

4. I observed that hitting \r in the RX(RST) field while no callsign is filled in caused an invalid QSO to be logged. An additional check has been added to prevent logging a QSO without callsign.

[AndyWLUG (andystewart)]

This has been fixed in xlog 2.0.6beta3.

[AndyWLUG (andystewart)]

Fixed in xlog 2.0.6beta3...soon to be released as xlog 2.0.6.

[AndyWLUG (andystewart)]

Version 2.0.6 was released in early March 2013, containing this fix.