Not only everything blinks but the background color changes to some middle
scale gray and that happens with all pdcurses demos
But that's minicom. I just tested with screen and they work just fine,
color included
I kind of remember now minicom had such problems with curses 15+ years
back. It seem
But using tmux, I am able to get pdcurses displays like this (it
actually has color):
File Debug Help
┌───Watch───┐
┌─┐│ │
│ ││ │
│ . *
││
Hey Johnny,
It has been a while since I ran the pdcurses with minicom, but my
recollection is that something sets attributes of the entire display to
blink all the time. Plus when drawing window borders using the VT100 /
ANSI line drawing character, you end up with a bunch of funky characters
On 2021-01-22 23:43, Gregory Nutt wrote:
Now examples compile and work although in flashing mode with minicom in
VT102 mode
If you start mincom with -t vt100 it should force VT100 vs VT102 mode.
But I thought that VT102 was mostly compatible?
The VT102 is a superset of the VT100. There are
Hey Greg,
I actully tried ALL of the emulation modes offered by minicom and each
one behaved the same.
I found that using Linux 'screen' or 'tmux' works, but neither of those
deal with the /dev/tty device "disappearing" suddenly.
Ken
On 1/22/21 2:43 PM, Gregory Nutt wrote:
Now examples
Now examples compile and work although in flashing mode with minicom in
VT102 mode
If you start mincom with -t vt100 it should force VT100 vs VT102 mode.
But I thought that VT102 was mostly compatible?
Yeah, I have never found a way to use pdcurses with minicom ... it
always has flashing characters like you stated.
Ken
On 1/22/21 2:10 PM, Grr wrote:
It also needs CONFIG_PDCURSES_MULTITHREAD or there's no PDC_ctx_free()
definition
Now examples compile and work although in flashing mode with
It also needs CONFIG_PDCURSES_MULTITHREAD or there's no PDC_ctx_free()
definition
Now examples compile and work although in flashing mode with minicom in
VT102 mode
I'll fix that later
Thanks again
Grr
El vie, 22 ene 2021 a las 14:35, Ken Pettit () escribió:
> Looks like changing nuttx/pdcdi
Looks like changing nuttx/pdcdisp.c:840 from "sp" to just "s" was the
only compile error. Though going through the exercise made me remember
that you also need to select:
Application Configuration --> Graphics Support --> pdcurses --> Input
Devices --> Terminal Input
Otherwise you don't ha
Sure, no problem!
Looking at the code, someone along the way changed the first calling
parameter in that function from "FAR SCREEN *sp" to "FAR SCREEN *s". In
my older copy of the NuttX code, the first parameter is "FAR SCREEN *sp".
Since I know the code pretty well, I can pull down the Apac
Thank you for your response
I searched menuconfig according to your instructions and found it.
Compilation crashed with
nuttx/pdcdisp.c:840:19: error: 'sp' undeclared (first use in this
function); did you mean 's'?
but it's a matter of debugging it. Maybe a lacking option, I'll research it
Than
Grr,
Actually, pdcurses has a mode that will work over serial using
System->Termcurses. This is a terminal based extension to pdcurses that
I added a few years back. It supports VT-100 / ANSI escape codes. I
haven't tested it in the Apache NuttX framework to validate it still
works though.
Hello all
Is there a way to have formatted text output over serial? I want to create
some testing utility that runs from nsh and has some screen organization to
ease use
I tested pdcurses examples but they seem to depend on fb (haven't analyzed
code) and all exited or crashed with "initscr(): Una
13 matches
Mail list logo
