Closed jxy closed 4 years ago
Are you using Windows? Would you be able to share a MWE so I can try to reproduce the issue?
No. It's macOS with qt term.
Simply doing surf(x, y, (x,y)->besselj0(y)*x^2, plotstyle="pm3d", gpcom=postcomm)
takes a couple of seconds at the first launch. Subsequent runs still take about a second.
On Sep 12, 2019, at 10:00 AM, mbaz notifications@github.com wrote:
Are you using Windows? Would you be able to share a MWE so I can try to reproduce the issue?
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
How many points are you plotting? Also: can you run the test described here and post the results (maybe in a gist if they're too long): https://discourse.julialang.org/t/standard-streams-much-slower-in-windows-than-in-linux/24924/3
It seems the initialization of the QT term takes a long time when there are lots of fonts available.
On Sep 13, 2019, at 11:15 AM, mbaz notifications@github.com wrote:
How many points are you plotting? Also: can you run the test described here and post the results (maybe in a gist if they're too long): https://discourse.julialang.org/t/standard-streams-much-slower-in-windows-than-in-linux/24924/3
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.
That would explain the issue. As a workaround, you may want to try the 'aqua' terminal which is native to MacOS.
I will add a command to allow the user to set the timeout. It'll be out in the next release.
Just to let you know that I'm also hitting this on my FreeBSD box with wxt term. It's just that the first plot takes a lot longer. Subsequent plots are fine.
@jxy I'll hurry with an update -- I've just been too busy lately.
Surface plot in a qt term always take longer on my computer, especially with larger sample/isosample. The setting for timeout is too optimistic in my opinion for something that throws error.
https://github.com/mbaz/Gaston.jl/blob/fb0ac116886d7d7d89633f8934058c94a0ad174b/src/Gaston.jl#L29
Perhaps just print out a warning every couple of seconds and keep reading until EOF?