On Tue, 20 Jul 2010, Jerry Dunmire wrote:
Some of the messages I'm trying to write to the status line are not
being displayed. I think this is because XmUpdateDisplay(text) is not
being called. That appears to be intentional because most
XmUpdateDisplay() calls have been commented out.
So, what is the preferred way to get a message displayed on the status
line? Should I just call XmUpdateDisplay() after the statusline() call
in order to force the update, or is there s better way?
I have this nagging feeling that I'm the one that commented out most
of those, but that was a few years back and I'm having difficulty
remembering details of what worked and what didn't. I guess I'd
recommend tracking down how incoming callsigns are being written to
the status line and using similar code.
This brings to mind something that I've wanted for a long time: A
separate LOG system that we could bring up in a viewer and write to
disk, plus roll over the logs like we do the others. We could
divorce ourselves somewhat from suggesting that people run Xastir
from an xterm when debugging problems. Some startup problems would
still necessitate starting from an xterm, most other problems would
not. Now... Why that came to mind from what you described above, I
haven't a clue! Another mystery as to how my mind works I guess.
--
Curt, WE7U. <http://www.eskimo.com/~archer>
APRS: Where it's at! <http://www.xastir.org>
Lotto: A tax on people who are bad at math. - unknown
Windows: Microsoft's tax on computer illiterates. - WE7U.
The world DOES revolve around me: I picked the coordinate system!"
_______________________________________________
Xastir-dev mailing list
[email protected]
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir-dev
