Changes

Jump to navigation Jump to search

FAQ

426 bytes added, 08:24, 27 July 2017
→‎Graphics: backends and toolkits: Overhaul section add answer how to change the current toolkit.
==What are the supported graphics backends?==
The * [https://www.opengl.org/ OpenGL] via the graphics toolkits '''[https://www.qt.io/ qt]''' (current default is OpenGL, through ) and '''[http://www.fltk.org/ fltk]'''* [http://www.gnuplot.info/ gnuplot] via the "qt" '''gnuplot''' graphics toolkit. The "ftlk" toolkit also relies on OpenGL.
Alternatively, Gnuplot can be used as a graphics backend by selecting the "gnuplot" ==How do I change my graphics toolkit.?==
==Why did you replace Gnuplot There are three commands to deal with an OpenGL backend?==graphics toolkits:
{| class="wikitable"| <code>available_graphics_toolkits</code>| lists all available graphics toolkits|-| <code>graphics_toolkit</code>| displays the currently used graphics toolkit|-| <code>graphics_toolkit ("qt/fltk/gnuplot")</code>| sets the graphics toolkit to either of [https://www.qt.io/ qt], [http://www.fltk.org/ fltk], or [http://www.gnuplot.info/ gnuplot], if available|} ==Why did you replace gnuplot with an OpenGL backend?== The development of Octave is committed to being both compatible with Matlab and adding additional features. Toward those ends, the development community has chosen developers decided to introduce a native OpenGL backend that supports Matlab handle graphics and its uicontrols. Starting with the 3.8 release, Octave uses OpenGL graphics by default (with [http://www.fltk.org/ FLTK widgets ] in Octave 3.8 and [https://www.qt.io/ Qt widgets ] in Octave 4.0 and later).
==Are there any plans to remove the gnuplot backend?==
'''No.''' There are no plans to remove the gnuplot backend. Even though the default graphics toolkit is now "qt", which uses OpenGL graphics with Qt widgets, the gnuplot backend It will still be available as long as our users find it useful.
==How can I implement a new graphics backend/toolkit?==
This is one of those times where the best documentation is to read the existing code. We have three different toolkits in Octave now, so there are some examples to draw from.

Navigation menu