Re: Out of Date bug for Qt terminal

[Daniel J S. <dan...@ie...>]

Thanks Mojca.  I relayed the thread link early this past weekend but 
haven't heard anything.  However, it looks like the information that 
someone was requesting.

Dan


On 08/25/2012 06:27 AM, Mojca Miklavec wrote:
> On Sat, Aug 25, 2012 at 6:31 AM, Daniel J Sebald wrote:
>> Mojca,
>>
>> Some others are experiencing bugs similar to what you report here:
>>
>> http://sourceforge.net/tracker/index.php?func=detail&aid=3469233&group_id=2055&atid=102055
>>
>> Why was this bug listed as "out of date"?
>
> I'm not sure why it was listed as "out of date" exactly, that's a
> question for Ethan, but that was on 11th January, 6 days before a
> major patch has been applied by Jérôme:
>
> 2012-01-17  Jérôme Lodewyck
>
>    * configure.in src/Makefile.am src/qtterminal/Makefile.am
>    src/qtterminal/QtGnuplotApplication.cpp
>    src/qtterminal/QtGnuplotApplication.h src/qtterminal/QtGnuplotEvent.cpp
>    src/qtterminal/QtGnuplotEvent.h src/qtterminal/gnuplot_qt.cpp
>    src/qtterminal/qt_term.cpp term/qt.trm: The Qt terminal application is
>    executed in a separate executable called gnuplot_qt, started by exec.
>    This makes the Qt terminal compatible with OS X.
>
> https://github.com/gnuplot/gnuplot/commit/a98002601bf690d0c37c47a7948c53a2096c20de
>
> It left some issues (like: Mac now sees two executables instead of one
> and draws both on dock, but one gets hidden afterwards; printing
> crashes). Some further trivial compilation issues which finally
> enabled compilation on Mac have been fixed after 4.6 release with
> commit on "2012-06-23 Jérôme lodewyck".
>
> https://github.com/gnuplot/gnuplot/commit/1da6c54924c275189a5954eeed8bb38e305b780f
>
> That second patch has not yet been imported into branch-4-6-stable (I
> really hope that they will end up in 4.6.1).
>
>> Did it resolve on its own, or is
>> this simply a case of having a fork in the process and the
>> debugger/compile-with-debug-code is unable to handle a fork.
>
> No, it was actually crashing and useless, it wasn't just about
> debugger. It didn't resolve on its own, it was the two patches listed
> above that made Qt usable on Mac. All in all, after end of june that
> bug report has actually been resolved, so there's no need to worry
> about it any more. It's just the ticket that has been closed "in
> advance" ;)
>
> Mojca
>
> (PS: I still believe that there must be a way to completely avoid fork
> on Mac, but I'm not experienced enough to figure it out how.)
>

-- 

Dan Sebald
email: daniel(DOT)sebald(AT)ieee(DOT)org
URL: http://www(DOT)dansebald(DOT)com