Re: Testing Qt5 on Mac

[Mojca M. <moj...@gm...>]

On Wed, Jul 17, 2013 at 7:25 PM, Ethan A Merritt wrote:
> On Wednesday, July 17, 2013 01:48:03 am Mojca Miklavec wrote:
>> Hi,
>>
>> just a few observations about testing Gnuplot with Qt5 on Mac:
>> - Printing now works (it didn't work with Qt4)
>
> So can we close bug 1079?

It's up to you and whether you consider Qt4 support obsolete or not.

MacPorts still doesn't package Qt4 and it's unlikely that it will do
any time soon (there are still a lot compile errors).

I'm afraid that this printing problem is only a manifestation of a
deeper problem with forking, but I don't know enough. Qt5 apparently
changed the whole model of how applications work, so it solved this
particular manifestation, but there are other "problems" now (empty
program icon that cannot be hidden, crash on exit on linux)

> On linux, gnuplot+Qt5 works smoothly right up until the time you exit
> the program.  Then the Qt5 exit handlers somehow get tangled up and cause
> a core dump even though the program is trying to exit cleanly.
> I haven't figured out how to disable or bypass the Qt5 exit handlers,
> or otherwise persuade them to not produce a core dump.
> Any ideas?

I don't know enough and this is a pure speculation, but I suspect that
a lot of problems would disappear if gnuplot could avoid forking.

Mojca