Re: win7: erratic console behaviour after first plot on wxt terminal

[Bastian M. <bma...@we...>]

Got it. wxt_waitforinput() was waiting for an event even when called 
with TERM_ONLY_CHECK_MOUSING. Now fixed in CVS.

   Bastian


Am 23.05.2014 06:47, schrieb Bastian Märkisch:
> This seems to be an effect of the event handling: gnuplot seems to wait
> for an event and blocks. Just moving the mouse inside plot window
> terminates the  "waiting" e.g. I will see if I can find the time to
> track this down over the weekend. IMHO this bug is release critical.
>
>     Bastian
>
>
> Am 22.05.2014 23:33, schrieb Karl Ratzsch:
>> Hi,
>>
>> this happens on win7 with the 5.0 binaries both from Tatsuro and the
>> older one from Bastian (so both with wxgtk2.8 and 3.0): After the
>> first plot on a wxt terminal, any command that is loaded from a file
>> can take several seconds. Function declarations, plots, whatever.
>> This only goes away when another terminal ist set, and resumes when
>> a new plot is done on wxt.
>>
>> The exact times are only reproducible with the exact same script,
>> and plots sometimes even get stuck and the script only resumes after
>> changing the focus back to the gp console window. Several commands
>> in one line (separated with ";") don´t seem to take longer that one.
>>
>> I´ve attached the script i used to probe this on three win7 machines.
>>
>> And this also works when a command including a linefeed is
>> copypasted into the console.
>>
>> It does not depend on uses privileges like the exit problem
>> https://sourceforge.net/p/gnuplot/bugs/1384/
>>
>> Best,
>>      Karl
>>