I've noticed a strange problem with multiplot on windows 7. When using the default qt terminal, first run "set multiplot" and immediately close the plotting window that opens. Then run "unset multiplot" and the program will freeze and require using the program not responding dialog box to close it. As it is possible to accidentally close this window, this could pose a problem.
I have encountered this problem with the 32 bit release candidate 3 and the 64 bit release candidate 2. The final release version of the 32 bit version (gp500-win32-mingw.zip in the 5.0 folder), seems to have fixed this. I don't want to report this as a bug, as it seems that it is likely fixed in the code base, but a 64bit final version is not yet available.
Will a 64bit version be released soon? I prefer to use the 64bit version, but don't want to use the latest release candidate as it has this bug. Based on the latest 32bit, I suspect that it is actually fixed, but hasn't made it to a 64bit version yet.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Scratch that. I did not notice that the newest release changed the default terminal to wxt. The problem IS still present when using the qt terminal. I will be reporting this as a bug.
Last edit: Matthew Halverson 2015-02-09
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I've noticed a strange problem with multiplot on windows 7. When using the default qt terminal, first run "set multiplot" and immediately close the plotting window that opens. Then run "unset multiplot" and the program will freeze and require using the program not responding dialog box to close it. As it is possible to accidentally close this window, this could pose a problem.
I have encountered this problem with the 32 bit release candidate 3 and the 64 bit release candidate 2. The final release version of the 32 bit version (gp500-win32-mingw.zip in the 5.0 folder), seems to have fixed this. I don't want to report this as a bug, as it seems that it is likely fixed in the code base, but a 64bit final version is not yet available.
Will a 64bit version be released soon? I prefer to use the 64bit version, but don't want to use the latest release candidate as it has this bug. Based on the latest 32bit, I suspect that it is actually fixed, but hasn't made it to a 64bit version yet.
Scratch that. I did not notice that the newest release changed the default terminal to wxt. The problem IS still present when using the qt terminal. I will be reporting this as a bug.
Last edit: Matthew Halverson 2015-02-09