|
From: Tatsuro M. <tma...@ya...> - 2019-02-22 01:39:45
|
----- Original Message -----
> From: Tatsuro MATSUOKA
> To: bmaerkisch
> Cc: gnuplot-beta
> Date: 2019/2/22, Fri 03:08
> Subject: Re: Aw: Re: README-Windows.txt
>
> Dear Bastian
>
>
>> I am a bit confused about your mail as it - in my view - adresses many
>> different somewh t independent topics. I will try to provide information
>> on all of them below.
>>
>>
>> * Status of the qt terminal on Windows
>>
>> qt is quite usable on Windows. It is definitively not "broken".
> It
>> does
>> have some quirks, though. One of them is related to fontconfig. For
>> whatever reason, the experience with fontconfig on Windows with gnuplot
>> has its difficulties: it reinitializes its cache very often, leading to
>> a simingly indefinitely delayed opening of the window (wxt used with
>> fontconfig) or an error message ("slow font initialisation" -
> qt).
>> This
>> is unsatisfactory and cannot be the "default" behaviour. So far I
>
>> could
>> not identify a remidy. We are certainly open to patches! Another issue
>> is Bug #1081: Qt: resizing makes plot "tremble/shake" which
> still
>> persists on Windows at least. Also we still have issues with detecting
>> the loss of communication with the outboard driver (or vice versa) in
>> some cases.
>>
>> If there are more issues with "qt" (which warrant to call it
>> "broken)
>> please let us know, so we can fix these issues.
This seem to be race condition.
I execute all.dem
GNUPLOT_LIB=../../demo GNUTERM=qt ./gnuplot all.dem < ../../../y.dat
y.dat is a file that contains many [CR].
In this case, plot is broken.
However we execute all.dem manually, ugly plot does not happen.
Sorry for noise.
Tatsuro
|