Re: PrintDlgEx [1/7]: Add common failure checks and a trace.

[Vitaly Lipatov]

What about move printdlgex related code in standalone file printdlgex.c?
Is it possible? I see printdlg.c too large already.

В сообщении от 18 сентября 2008 Gal Topper написал(a):
> Changes since last attempt:
> 1) Added a comment to explain the rationale behind the CommonChecks
> function. 2) Resources and header are no longer in separate patches.
> Instead, they are added along with the code that requires them.
> 3) Some unused elements are no longer added in this patch-set.

-- 
Vitaly Lipatov, ALT Linux Team
Russia, Saint-Petersburg, www.etersoft.ru

PrintDlgEx [1/7]: Add common failure checks and a trace.

[Gal Topper]

There's some code sharing between PrintDlg and PrintDlgEx, and a
potential for more, but it's definitely _possible_ to separate them
into two different files. I'm not sure it's the best thing to do
though.

On Thu, Sep 18, 2008 at 1:55 PM, Vitaly Lipatov <lav(a)etersoft.ru> wrote:
> What about move printdlgex related code in standalone file printdlgex.c?
> Is it possible? I see printdlg.c too large already.
>
> В сообщении от 18 сентября 2008 Gal Topper написал(a):
> > Changes since last attempt:
> > 1) Added a comment to explain the rationale behind the CommonChecks
> > function. 2) Resources and header are no longer in separate patches.
> > Instead, they are added along with the code that requires them.
> > 3) Some unused elements are no longer added in this patch-set.
>
> --
> Vitaly Lipatov, ALT Linux Team
> Russia, Saint-Petersburg, www.etersoft.ru