[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #37795] FLTK unresponsive when readline is dis

From: Mike Miller
Subject: [Octave-bug-tracker] [bug #37795] FLTK unresponsive when readline is disabled
Date: Fri, 28 Mar 2014 13:54:55 +0000
User-agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/33.0.1750.152 Safari/537.36

Follow-up Comment #7, bug #37795 (project octave):

Or run FLTK in a separate process and communicate over a pipe. Wait... :)

I propose a check in __init_fltk__ similar to the one that is done now to
ensure DISPLAY is set, that should fail if readline is not enabled. I'm not
sure how to check whether readline is enabled at the moment since it's
intentionally hidden behind an abstract interface, but I'm willing to take a
look at that if no one else gets to it first.

It's really the fact that functions added to add_input_event_hook will never
be executed when readline is disabled. Maybe there should be some generic
function to tell whether the input_event_hook is active, rather than
conflating it with readline being enabled?


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]