From: Daniel J S. <dan...@ie...> - 2012-08-22 14:10:57
|
On 08/22/2012 04:05 AM, Mojca Miklavec wrote: > On Wed, Aug 22, 2012 at 10:21 AM, Daniel J Sebald wrote: >> On 08/22/2012 02:37 AM, Mojca Miklavec wrote: >>> >>> On Wed, Aug 22, 2012 at 5:39 AM, Daniel J Sebald wrote: >>>> >>>> What is the status of the Qt terminal? It easily builds and works on >>>> linux systems. How about Apple? >>> >>> >>> The trunk code finally compiles (since the patch on "2012-06-23 >>> Jérôme lodewyck"), but it would be nice if that commit could be >>> included in branch-4-6-stable before next release. >> >> I assume there is a Qt init step that will check that the system has Qt >> support available and active. > > I'm not sure if I understood the question properly. If the Qt terminal is included with the next release and the user doesn't have Qt operational on his or her system, what will happen? That's all I meant. >>> There are some issues with forking, most annoying is that printing >>> crashes while opening printing dialog. (If I try to circumvent the >>> printing dialog, it prints fine.) I have no idea where to look to fix >>> it. Two programs open on dock, but one icon gets hidden. Suboptimal, >>> but acceptable. >> >> The fork influences Qt printing? Strange. > > I'm not 100% sure about that, but that's the only explanation I have. > It crashes here: > > QPrinter printer; > if (QPrintDialog(&printer).exec() == QDialog::Accepted) > > and the same command works flawlessly if I write a simple hello world > application. Also, if I skip the QPrintDialog and just print (that is: > if I modify and recompile source) it starts working. It might or might > not be connected with forking, but I have no clue where to look. > Here's what gets printed into gnuplot screen: > > gnuplot_qt[69041]<Error>: kCGErrorIllegalArgument: _CGSFindSharedWindow: WID -1 > gnuplot_qt[69041]<Error>: kCGErrorFailure: Set a breakpoint @ > CGErrorBreakpoint() to catch errors as they are logged. > gnuplot_qt[69041]<Error>: kCGErrorIllegalArgument: > CGSSetWindowShadowAndRimParametersWithStretch: Invalid window > 0xffffffff > > But printing is not critical. The _CGSFindSharedWindow WID -1 sure would make one think it might be a fork() issue. Fork is supposed to replicate the current process stack/state, but perhaps that doesn't apply to what is happening in the Qt library. Maybe another Qt initialization needs to be done for the forked process? Just guessing. Dan |