|
From: sfeam <sf...@us...> - 2014-02-27 06:04:15
|
On Wednesday, 26 February 2014 11:29:52 PM Daniel J Sebald wrote: > Why couldn't the terminal API have a timeout specifier, i.e., > > int qt_waitforinput(int ms) > > and then only have the Qt terminal pertinent code while gnuplot core > watches for the other input routes? Why would there be a timeout? If you are waiting for the user to finish inspecting their plot before continuing, that could take a long time. They might even go off for lunch before deciding to hit <cr> or click the mouse. They'd be rather annoyed if they came back from lunch to find that the plot had disappeared or was no longer selectable. Anyhow, it seems like as of today we have Qt working on all three platforms with maybe some quirks about slow font handling on OSX that we probably can't do a whole lot about. The one bit that I would say is still unsatisfactory in the Qt terminal is the fact that you can't set a size preference, the size you manually set via "set term qt size XX,YY" is ignored, and any resizing you do using the mouse is not persistent. If you can figure out how to fix that then Mojca and I at least would be happier, and probably future Qt users as well. Ethan |