Fix search panel size #472
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
#459 brought up a hidden issue: in order to everything work correctly search panel was initialized twice. First to ensure that the startup messages are shown and then according to the actual CONTEST_MODE configuration.
The second initialization has been suppressed, so we were left with the 9-band non-contest search panel.

And there is no way to get it reduced to 6. :CONtest command merely switches
iscontest
, doesn't resize the panel.The solution is to drop the early initialization and call ncurses' plain
refresh()
in showmsg.c. There are no panels at this point yet, so no use calling outrefreshp()
(=update_panel() + co).Getting back to :CONtest - it still can't switch panel size according to
iscontest
.My view is that this feature is not needed: one shall not switch contest mode while already running TLF. This is a task to be done when configuring a contest or simple QSO setup, before starting TLF.
Taking it one step further, :CFG/:SET shall also be removed (see the long runner #233). As I see we have practically no chance to cleanly restart the program as there is a number of allocated data structures, TCP and serial connections, etc. to be (really) correctly freed and set up anew. User shall simply restart TLF on such configuration changes. It takes just 1 second. (ok, plus the 3 seconds cluster wait, but that's another story...)