-
Notifications
You must be signed in to change notification settings - Fork 31
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix search panel size #472
Conversation
was always using non-contest mode (9 bands) switched to plain refresh() in showmsg.c has_room_for_message() is bool
I see the problem.
That will work as long as anybody uses Other ways would be to allow resizing of the searchwindow, having a dummy panel or using an early init for the keyer panel. But I assume it is not worth the work here.
That would need a
+1 from my side. |
I will add a comment to As far as I understand
|
Just merge it in afterwards.
Yes that seems to be the case - just look at the first lines of At the time I picked up TLF (around '09) there were three terminals - the default one used during startup, a 'packetscreen
One of the reasons were that 'newterm' was not designed to handle different screen layouts on the same physical display but to switch between different physical consoles. So I dropped the second
Ok. Sounds sensible. |
#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...)