|
From: | Rik |
Subject: | [Octave-bug-tracker] [bug #60509] First initialization of graphics subsystem switches graphics_toolkit when octave-cli used |
Date: | Mon, 3 May 2021 17:30:30 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.72 Safari/537.36 |
Follow-up Comment #7, bug #60509 (project octave): I wish I knew the programmer's original intent. One way to tackle this would be to change get_toolkit(). Another would be to change register_toolkit () void gtk_manager::register_toolkit (const std::string& name) { if (dtk.empty () || name == "qt" || (name == "fltk" && available_toolkits.find ("qt") == available_toolkits.end ())) dtk = name; available_toolkits.insert (name); } so that registering a toolkit also made it the default to the gtk_manager (not the default to Octave which would use whatever was set by graphics_toolkit(). Yet another choice would be to change how init_toolkit works. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?60509> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |