[Top][All Lists]

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

Re: Deprecate fltk graphics toolkit?

From: Pantxo
Subject: Re: Deprecate fltk graphics toolkit?
Date: Wed, 8 Nov 2017 05:25:53 -0700 (MST)

John W. Eaton wrote
> As I understand it, there are some issues with starting Qt graphics when 
> running in non-gui mode, and that the fltk graphics toolkit does not 
> have those problems.  But if we could fix that, and make the Qt plot 
> window work when running in --no-gui mode, could we deprecate the fltk 
> graphics toolkit?
> It seems wasteful to have to maintain both Qt and fltk graphics.  For 
> example, I just made a change for the "Save" and "Save As" menu items in 
> the Qt graphics code.  This change took much longer than it should have 
> when I remembered that the change would also need to be made in the fltk 
> graphics code and that needed to be done in a completely different way.
> Comments?
> jwe

I am in favor of removing FLTK but first we should ensure we have a way to
run Octave interpreter and Qt figures in the same thread, which is currently
not possible. The main reason is that comparing FLTK and Qt is currently the
best way to determine wether a graphics bug is due to thread management or
to core opengl code. Basically "octave --no-gui" would be single-threaded
"octave" would be multi-threaded.

That would also raise the question wether we want to continue using readline
event loop (callback based mechanism) for Qt figures->interpreter
communication or make a transition to use Qt event loop (signal/slot


Sent from: http://octave.1599824.n4.nabble.com/Octave-Maintainers-f1638794.html

reply via email to

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