From what worked in FLTK2, I don't think we want or need per-class styles.
All customization I have seen involved changing the Widget style (the
base class) and the 2 or 3 per-class ones who's only reason for
existence was that the default values were different. I suggest this be
fixed by
I had some time this weekend to make a variation that works
with interactive programs like gdb(1). It's unix only,
but handles stdin, stdout, and stderr asynchronously:
http://seriss.com/people/erco/fltk/unix-bidir-dumb-terminal.cxx
It uses pthreads and
On 29.08.2011, at 02:37, Greg Ercolano wrote:
I had some time this weekend to make a variation that works
with interactive programs like gdb(1). It's unix only,
but handles stdin, stdout, and stderr asynchronously:
Cool! Thanks you!
On 08/29/11 01:26, MacArthur, Ian (SELEX GALILEO, UK) wrote:
The example opens up a tcsh prompt.
See, that's gotta be a bug, right there! ;-)
You're right, it is a bug.. in bash!
During dev, I was getting inconsistent behavior from bash
on an old OSX 10.4.11
On 08/29/11 01:26, MacArthur, Ian (SELEX GALILEO, UK) wrote:
It uses pthreads and bidirectional pipe(2)s. All FLTK operation
is handled by the parent; the threads are just data pumps.
[I chose not to use add_fd() to facilitate a Windows port]
On WIN32, add_fd() will work OK
