Menu
▾
▴
gnuplot-beta
|
From: Karl R. <ra...@un...> - 2014-05-22 22:15:59
Attachments:
test.plt
|
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 -- Karl-Friedrich Ratzsch (Dipl. Chem.) Freiburger Materialforschungszentrum, Universität Freiburg Stefan-Meier-Straße 21, 79104 Freiburg i. Br. Tel.: 0761/203-4748 Fax: -4701 |
|
From: Tatsuro M. <tma...@ya...> - 2014-05-22 23:28:19
|
--- On Fri, 2014/5/23, Karl Ratzsch wrote: > 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 Hello Thank you for the feed back. The origin of problem that you pointed out is the same that was pointed out by Tait. http://gnuplot.10905.n7.nabble.com/Gnuplot-version-5-release-candidate-td18424.html#a18437 I have quickly downgrade the cvs source before the change 2014-01-04 but the change there seemed not to be the origin of the problem. We have to go back and search which change is the origin of the problem. Your bug report might be useful for searching the origin. Regards Tatsuro |
|
From: Tatsuro M. <tma...@ya...> - 2014-05-23 00:26:41
|
--- On Fri, 2014/5/23, Tatsuro MATSUOKA wrote: > --- On Fri, 2014/5/23, Karl Ratzsch wrote: > > 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 > > Hello > > Thank you for the feed back. The origin of problem that you pointed out is the same that was pointed out by Tait. > > http://gnuplot.10905.n7.nabble.com/Gnuplot-version-5-release-candidate-td18424.html#a18437 > > I have quickly downgrade the cvs source before the change 2014-01-04 but the change there seemed not to be the origin of the problem. > > We have to go back and search which change is the origin of the problem. > > Your bug report might be useful for searching the origin. Mmmm. The issue that you pointed out is different from that I have met. The all.dem script work correctly on 4.6.5 binary build by Bastian. Perhaps two different issues exist for wxt terminal on gnuplot for windows. Tatsuro |
|
From: Tatsuro M. <tma...@ya...> - 2014-05-23 00:16:52
|
--- On Fri, 2014/5/23, Karl Ratzsch wrote: > 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. The contests of the 'test.plt' is : tand(gp,gpp) = (gp<0?1/0:gpp<0?1/0:abs(log10(gp/gpp)) > 2 ? 1/0 : gpp/gp) This is an only function. No plot command I can see. Tatsuro |
|
From: Bastian M. <bma...@we...> - 2014-05-23 04:47:41
|
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 > |
|
From: Bastian M. <bma...@we...> - 2014-05-24 07:51:43
|
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 >> |
|
From: Tatsuro M. <tma...@ya...> - 2014-05-24 11:00:09
|
--- On Sat, 2014/5/24, Bastian Märkischwrote: > 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 > >> > > I have confirmed the fix. Thanks! I will update my binary distribution on Monday. Tatsuro |
|
From: Tatsuro M. <tma...@ya...> - 2014-05-26 00:40:30
|
--- On Sat, 2014/5/24, Tatsuro MATSUOKA wrote: > --- On Sat, 2014/5/24, Bastian Märkischwrote: > > Got it. wxt_waitforinput() was waiting for an event even when called > > with TERM_ONLY_CHECK_MOUSING. Now fixed in CVS. > > > > Bastian > I have confirmed the fix. Thanks! > I will update my binary distribution on Monday. > I have updated the binary on my website. Karl Ratzsch. Please confirm whether the fix by Bastian are fix your problem or not. Tatsuro |
|
From: Tatsuro M. <tma...@ya...> - 2014-05-26 10:10:52
|
This is forwarded message. --- Karl Ratzsch wrote: > From: Karl Ratzsch > Subject: Re: win7: erratic console behaviour after first plot on wxt terminal > To: "Tatsuro MATSUOKA" > Date: Mon, 26 May 2014 10:35:51 +0900 > > On 26.05.2014 02:40, Tatsuro MATSUOKA wrote: > > I have updated the binary on my website. > > > > Karl Ratzsch. > > Please confirm whether the fix by Bastian are fix your problem or not. > > > > Problem definitely sems fixed, scripts run much faster now. Thanks! > > The test script i attached last week was the wrong one, of course, > the original one timed some commands with time(). Sorry. > > Best, > Karl > > -- > Karl-Friedrich Ratzsch (Dipl. Chem.) > Freiburger Materialforschungszentrum, Universität Freiburg > Stefan-Meier-Straße 21, 79104 Freiburg i. Br. > Tel.: 0761/203-4748 Fax: -4701 > |
|
From: Tatsuro M. <tma...@ya...> - 2014-05-24 21:00:19
|
--- On Sat, 2014/5/24, Bastian Märkisch wrote: > 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 > >> > Hello Karl Prof. Kakuto prepared a new snapshot gnuplot-5.0rc1 on http://ctan.ijs.si/mirror/w32tex/w32/ gnuplot-50plrc1w32.zip Note that the default terminal on his binary is windows terminal. You can use wxt or qt terminal explicitly set set term wxt or set term qt Please confirm whether your problem is solved in the new snapshot binary. Tatsuro |
