Re: Review Request 125681: Correctly set the printSetting's parent

2015-10-20 Thread Robby Stephenson
--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/125681/ --- (Updated Oct. 20, 2015, 11:08 p.m.) Status -- This change has been

Re: Review Request 125681: Correctly set the printSetting's parent

2015-10-19 Thread Michael Pyne
--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/125681/#review87107 --- Ship it! Looks reasonable to me, so I'd implement as long as

Re: Review Request 125681: Correctly set the printSetting's parent

2015-10-18 Thread Robby Stephenson
--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/125681/ --- (Updated Oct. 18, 2015, 8:58 p.m.) Review request for KDE Frameworks and

Review Request 125681: Correctly set the printSetting's parent

2015-10-17 Thread Robby Stephenson
--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/125681/ --- Review request for KDE Frameworks and Martin Tobias Holmedahl Sandsmark.

Re: Review Request 125681: Correctly set the printSetting's parent

2015-10-17 Thread Michael Pyne
--- This is an automatically generated e-mail. To reply, visit: https://git.reviewboard.kde.org/r/125681/#review86991 --- Ship it! I agree that the current code is broken, and that

Re: Review Request 125681: Correctly set the printSetting's parent

2015-10-17 Thread Michael Pyne
> On Oct. 18, 2015, 1:52 a.m., Michael Pyne wrote: > > I agree that the current code is broken, and that your fix makes sense > > given the surrounding comments clarifying ownership. But why not simply > > construct the print settings object with the dialog as a parent? I see no > > reason

Re: Review Request 125681: Correctly set the printSetting's parent

2015-10-17 Thread Robby Stephenson
> On Oct. 18, 2015, 1:52 a.m., Michael Pyne wrote: > > I agree that the current code is broken, and that your fix makes sense > > given the surrounding comments clarifying ownership. But why not simply > > construct the print settings object with the dialog as a parent? I see no > > reason