Hi Andre,
According to my test plan of the registry merging project, I will add
new tests for HKCR. At first I tried to add them to the old code but I
find it become too long and hard-reading. I had to rewrite them to a
series of strict and neat tests, classified as read/write operations,
including
On Wed, May 22, 2013 at 4:19 PM, Alan W. Irwin
wrote:
> On 2013-05-22 14:31-0700 Austin English wrote:
>
>> This is better suited for the forum, but:
>>
>> http://wiki.winehq.org/RegressionTesting#head-a7150fa43baeaab304403f27a930647ea13648b7
>
>
> Hi Austin:
>
> Thanks for that reference which is
On 2013-05-22 14:31-0700 Austin English wrote:
This is better suited for the forum, but:
http://wiki.winehq.org/RegressionTesting#head-a7150fa43baeaab304403f27a930647ea13648b7
Hi Austin:
Thanks for that reference which is helpful for a git newbie like
myself. I had some additional questions,
On Wed, May 22, 2013 at 2:03 PM, Alan W. Irwin
wrote:
> Generally I have found in still fairly limited testing that MSYS
> bash.exe redirection is fine on wine-1.5.30 (which I have now been
> able to build in 32-bit mode on Debian wheezy x86_64 thanks to the
> 32-bit library symlink trick discusse
Hi,
Is there any problem with these patches?
http://source.winehq.org/patches/data/96314
http://source.winehq.org/patches/data/96328
Christian
Generally I have found in still fairly limited testing that MSYS
bash.exe redirection is fine on wine-1.5.30 (which I have now been
able to build in 32-bit mode on Debian wheezy x86_64 thanks to the
32-bit library symlink trick discussed in my previous recent thread).
However, I have just discover
On Tue, May 21, 2013 at 02:52:55PM -0600, Charles Davis wrote:
> You can't return the straight HRESULT from ForceFeedback here. That's because
> the codes in the FACILITY_NULL range on Mac get their values from the 16-bit
> COM runtime (cf. ). You must turn them into
> their corresponding Win32
To anybody interested,
I think I've found a solution to an old problem of implementing winmm
joystick support in WINE for Mac, but lack the necessary skills and
experience to code it up myself. WINE-Linux has had it implemented for
awhile, but it was never coded up for OS X. winmm is an older inte
On 21 May 2013 21:09, Stefan Dösinger wrote:
> Am 2013-05-21 16:03, schrieb Henri Verbeet:
>> On 21 May 2013 13:18, Stefan Dösinger
>> wrote:
>>> +static void test_coop_level_versions(void)
>> It may make more sense to move that to ddraw2.c and ddraw4.c
>> instead.
> The reasoning behind putting
On 22 May 2013 11:20, Stefan Dösinger wrote:
> The attached patch passes all the tests without todo_wine. However,
> I'm not sure if there are any unintended side effects when I change
> the order of the swapchain re-creation and focus window
> release/acquire. I'll probably put this into a differ
2013/5/22 Stefan Dösinger
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Am 2013-05-22 10:59, schrieb Christian Costa:
> > *"You are not allowed to analyze Windows files with the trace
> > functions of Wine"
> E.g. when you are working on Wine's d3dx9 implementation, you
> shouldn't use na
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am 2013-05-22 10:59, schrieb Christian Costa:
> *"You are not allowed to analyze Windows files with the trace
> functions of Wine"
E.g. when you are working on Wine's d3dx9 implementation, you
shouldn't use native d3dx9.dll and create a +d3d9 log to se
*Hi,
*
*I read on the GSoC page this:
*
*"You are not allowed to analyze Windows files with the trace functions of
Wine"
*
*What does that mean?
*
*Thanks
*
*Christian
*
On Tue, May 21, 2013 at 11:03 PM, Alexandre Julliard
wrote:
> You shouldn't need 2 server calls for this.
>
> There's no reason to abort on every failure.
An improved version is sent, thanks a lot for review!
--
Regards,
Qian Hong
-
http://www.codeweavers.com
14 matches
Mail list logo
