On 17 February 2014 14:04, Knoll Lars wrote:
> I¹ve been discussing a bit with Friedemann and Andy on IRC, and I¹m
> willing to give this change set an exception to the feature freeze. The
> reason is that I believe that this significantly improves our level of
> support in this area, and that th
>
> John Layt sayeth:
>
> >As noted on the Releasing list, I didn't get the OSX 10.7 blocker bug
> >fixed in
> >time, and using just the layout code without the plugin proved too much
> >work
> >to be stable in time, so *none* of this change set has made it for 5.3.
>
,
> >Thoughts?
>
Knoll Lar
On 17/02/14 13:47, "John Layt" wrote:
>On Wednesday 12 Feb 2014 15:37:29 John Layt wrote:
>> On Wednesday 12 Feb 2014 12:03:53 John Layt wrote:
>
>> > Sorry, needed to wait until the full stack of changes had been
>>completed
>> > and integrated before pushing. The revised patches are up for revi
On Wednesday 12 Feb 2014 15:37:29 John Layt wrote:
> On Wednesday 12 Feb 2014 12:03:53 John Layt wrote:
> > Sorry, needed to wait until the full stack of changes had been completed
> > and integrated before pushing. The revised patches are up for review, I'm
> > not sure we'll get it done in time,
> * Keep the patches switching to the new platform plugin code in reserve to
> either switch for 5.3 if testing proves the plugin is stable enough, or more
> likely to use in 5.4 if not.
I like this idea at least, because this enables the reviews to keep going and
we can keep testing until we are
Hi,
>The main issues outstanding I see:
My finding using Windows 8.1 / HP Color LaserJet 6030 MFP PS Class
Driver is that the default paper size is B5 (instead of letter/A4) and
it simply does not print (using A4), although the code calling
EndPage/EndDoc is executed.
Friedemann
--
Fri
On Wednesday 12 Feb 2014 12:03:53 John Layt wrote:
> On Monday 10 Feb 2014 17:07:11 Shaw Andy wrote:
> > Since the feature freeze is on the 14th I have been eagerly awaiting the
> > changes that have been indicated already have been done so I can carry on
> > testing. Have I missed some updates or
On Monday 10 Feb 2014 17:07:11 Shaw Andy wrote:
>
> Since the feature freeze is on the 14th I have been eagerly awaiting the
> changes that have been indicated already have been done so I can carry on
> testing. Have I missed some updates or something? I am concerned because I
> know how many peop
> > >I’ve now gone through all changes. The set looks pretty good overall, and
> > >testing on Linux showed no regressions compared to 5.2.
> >
> > One correction here: The paperRect as shown in the preview of the dialogs
> > manual test shows some slightly different results, that look like a
> > r
> >I’ve now gone through all changes. The set looks pretty good overall, and
> >testing on Linux showed no regressions compared to 5.2.
>
> One correction here: The paperRect as shown in the preview of the dialogs
> manual test shows some slightly different results, that look like a
> rounding iss
On 05/02/14 13:59, "Knoll Lars" wrote:
>Hi John,
>
>I’ve now gone through all changes. The set looks pretty good overall, and
>testing on Linux showed no regressions compared to 5.2.
One correction here: The paperRect as shown in the preview of the dialogs
manual test shows some slightly differe
Hi John,
I’ve now gone through all changes. The set looks pretty good overall, and
testing on Linux showed no regressions compared to 5.2.
IMO, you can go ahead and stage the first set of changes that are mainly
cleanups.
There are quite a few comments on the changes adding the new public API.
On 30 Jan 2014, at 01:15, John Layt wrote:
>
> I've just pushed a 33 commit change set for this to Gerrit, my apologies to
> the people I've tagged as reviewers :-) Any one else interested, feel free
> to
> jump in and help.
>
> There's 4 main new classes:
> * QPageSize
> * QPageMargins
> *
Hi John,
Thanks a lot for all your work. I¹ll have a look at the changes as well.
Cheers,
Lars
On 30/01/14 01:15, "John Layt" wrote:
>On Monday 06 Jan 2014 22:40:44 you wrote:
>
>> My aims for the 5.3 release will be to
>> * Define the new qpa print device api and implement support for the 3
>
On Monday 06 Jan 2014 22:40:44 you wrote:
> My aims for the 5.3 release will be to
> * Define the new qpa print device api and implement support for the 3
> core platforms
> * Use this new class in QPrinterInfo and QPrintEngine to replace the
> current print device code, ensuring behaviour is cons
John Layt sayeth:
> Hi,
>
> I've spent the last few weeks going over the current print support and
> trying to map out a plan to improve things. ,
Given my limited time, I've decided to take a different approach to
> try build the new code over the next few releases as a new set of QPA
> classe
Hi,
I've spent the last few weeks going over the current print support and
trying to map out a plan to improve things. We've long intended to
create a new QtPrint module to replace QtPrintSupport in which we
separate the painting code from the print job management code and
support a more modern w
17 matches
Mail list logo
