Hello developers.

Thank you for all your work and effort.  

This is what appears to be a bug in auto sequencing in v.2.3.0-rc2.   Sequencing used to be virtually flawless with v2.2.2.

After getting an RR73, instead of sending a 73, my side sent a -15 (just the report).

Please see picture attached.

Thanks.
Carl - WC4H

Sequencing errors are easily induced in v2.2.2 od9b96 as follows:
While in a QSO with contact one, double-click in the left window on another contact then immediately double-click on the last received transmission from contact 1 in the right window.

If this action is taken following a received RR73, a 73 should be sent but isn't.
Instead, an RR73 is sent.

If this action is taken following a received initial signal report, the correct R+ signal report is next sent but then does not advance to the 73 message after receiving an RR73 and instead remains stuck sending another R+ signal report.

Hi Kevin.

I highlighted the wrong error... if you see the line below the RR73, my system sent a CQ.. I had to hit the 73 manually.  I posted it after having saved the screen and looked at it crossed eye.

Still a sequencing error.

Thanks.
Carl - WC4H

The thing is that there have been sequencing errors creeping in.

Here's another where I should have been going to CQ but a 73 was sent.