|
From: Ethan A M. <sf...@us...> - 2014-02-27 00:38:48
|
On Wednesday, 26 February, 2014 18:04:14 Allin Cottrell wrote: > On Wed, 26 Feb 2014, Mojca Miklavec wrote: > > > On Wed, Feb 26, 2014 at 9:54 PM, Ethan A Merritt wrote: > >> On Wednesday, 26 February, 2014 09:24:37 Mojca Miklavec wrote: > >>> After applying your first patch only the first gnuplot run took half a > >>> minute to start. Subsequent runs take 4 seconds at most which is > >>> totally acceptable. > >> > >> OK, I have applied that first patch for #ifdef Q_OS_MAC only. > > > > Thank you, it works fine now. But is it on purpose that every mac/qt5 > > user will now get the following printed? > > > > Terminal type set to 'qt' > > gnuplot> plot cos(x) > > Error: short read from gnuplot_qt socket while expecting font metrics > > Error: short read from gnuplot_qt socket while expecting font metrics > > gnuplot> > > Yes, because users of qt5 on Macs are a big nuisance and deserve to > be punished. Not. > > What do you think? Maybe it has to do with debugging? If, perchance, > that might be needed ;-) All of the qDebug() messages are of the "this is not supposed to happen" variety. The one above does not trigger on windows or linux, and if I understand correctly does not trigger on OSX with Qt4 either. Whether it points to a problem with Qt5 per se or to a larger problem with OSX font handling I do not know, but either way it really is fingering a fixable problem. If nothing else it should allow OSX users to diagnose semi-quantitatively whether tweaks to their font setup improve or degrade the performance. Ethan |