D]> 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
fy-translation switch. Just take the wrc command that make is
> running in that directory and append --verify-translation to it. Do that
> before and after you applied your patch. If you see additional lines
> popping up that start with "DIFF" or "ERR" your patch breaks t
Hi Juan,
I indeed submitted a set of tests that included these cases. Specifically:
http://www.nabble.com/PrintDlgEx-tests--7-9-%3A-Add-tests-for-PD_RETURNDEFAULT.-td19293210.html#a19293210
http://www.nabble.com/PrintDlgEx-tests--9-9-%3A-Add-a-test-for-PD_RETURNDEFAULT-that-is-specific-to-PrintD
Hi everyone,
I'm glad to say that my project to implement PrintDlgEx* went very
well, as I've implemented almost everything by the deadline, and have
test cases for every meaningful non-interactive scenario, AFAICT. The
only feature that I have not had time to implement and test is the
lpCallbac
http://www.winehq.org/site/docs/wine-faq/index#WHAT-DO-I-NEED-IN-ORDER-TO-USE-WINE
Not an answer specific to ARM, but this section of the FAQ describes
the situation with respect to running Windows applications on non-x86
platforms using Wine.
-Gal
On Fri, Aug 8, 2008 at 8:05 PM, Tomasz Czapiews
Hi, and sorry for missing this mail and responding late,
My project to implement PrintDlgEx() has been going well in that I've
implemented everything but the custom property pages feature (and ANSI
support). Therefore, at this point, my main challenge is to implement
this feature and to ensure goo
> Could the students come forward and say something about themself?
Hello everyone. My name is Gal Topper and my goal this summer will be
to implement PrintDlgEx* in Wine, so that we'll have support for the
newer and more flexible print dialog that was introduced in Windows
NT. I am a th
