On 3/27/2013 00:10, Daniel Jeliński wrote:
2013/3/26 Nikolay Sivov :
Is there any reliable way to test send mouse messages? Cause it looks like
if I send WM_LBUTTONDOWN directly it doesn't trigger tab selection code on
windows, but works in wine.
Do you want to figure out the correct sequence o
On 3/27/2013 09:05, Alistair Leslie-Hughes wrote:
Hi,
Changelog:
iads.idl: Add missing interfaces
Best Regards
Alistair Leslie-Hughes
+typedef enum
+{
+ADS_SEARCHPREF_ASYNCHRONOUS = 0,
+ADS_SEARCHPREF_DEREF_ALIASES= 1,
You don't need to do it manually, widl will generate
On Tue, Mar 26, 2013 at 6:04 PM, Michael Mc Donnell
wrote:
> On Tue, Mar 26, 2013 at 7:07 PM, Nozomi Kodama
> wrote:
>>
>> Why are they not committed yet?
>
>
> Alexandre is on vacation so that might explain why :-)
Well, he was last week, back now, but there is a backlog of patches to
go throug
On Tue, Mar 26, 2013 at 7:07 PM, Nozomi Kodama wrote:
> Why are they not committed yet?
>
Alexandre is on vacation so that might explain why :-)
Hi Ken,
Thank you for your explanation. I now have a far better understanding of the
relationship between kernel32 and user32. The information was actually on
MSDN, but I didn't really pay too much attention to the prerequisites for using
calls such as SystemParametersInfo.
I'm now going to s
Why are they not committed yet?
From : Matteo Bruni
Object : Re: d3dx9 [patch 1/2, try 3]: Implement D3DXSHEvalSphericalLight
2013/3/15 Nozomi Kodama :
>
Patch series is fine to me.
>This won't be able to work. The linker error is telling you,
effectively, that you're not importing user32. However, kernel32 can't
import user32. Kernel32 is at a lower level than user32. And a console
program especially can't rely on user32 being loaded and initialized to
satisfy the request
2013/3/26 Nikolay Sivov :
> Is there any reliable way to test send mouse messages? Cause it looks like
> if I send WM_LBUTTONDOWN directly it doesn't trigger tab selection code on
> windows, but works in wine.
Do you want to figure out the correct sequence of messages or write
tests for wine's tes
Austin English writes:
> diff --git a/dlls/msvcr110/msvcr110.spec b/dlls/msvcr110/msvcr110.spec
> index 4a94dbe..babfc67 100644
> --- a/dlls/msvcr110/msvcr110.spec
> +++ b/dlls/msvcr110/msvcr110.spec
> @@ -928,7 +928,7 @@
> @ stub -arch=i386,win64 __crtLCMapStringEx
> @ cdecl __crtLCMapStringW(
On Mon, 18 Mar 2013, Ken Thomases wrote:
[...]
> Currently, you have to set a registry key to enable the Mac driver:
>
> [HKEY_CURRENT_USER\Software\Wine\Drivers]
> "Graphics"="mac,x11"
An issue I ran into with the registry approach is that it causes Wine to
use X11 to show the 'Updating the Win
On Tue, Mar 26, 2013 at 04:50:03PM +0100, Alexandre Julliard wrote:
> Ah OK, I guess that makes it a PITA to test...
Some kind of print-scan magic comes to mind ;-)
Huw Davies writes:
> On Tue, Mar 26, 2013 at 04:30:14PM +0100, Alexandre Julliard wrote:
>> Huw Davies writes:
>>
>> > Ideally this would be done in wineps.drv, but by that point the conversion
>> > to device units would cause rounding errors.
>>
>> What about GetTextExtent functions? Do the
On Tue, Mar 26, 2013 at 04:30:14PM +0100, Alexandre Julliard wrote:
> Huw Davies writes:
>
> > Ideally this would be done in wineps.drv, but by that point the conversion
> > to device units would cause rounding errors.
>
> What about GetTextExtent functions? Do they need this too? Some test
>
Huw Davies writes:
> Ideally this would be done in wineps.drv, but by that point the conversion to
> device units would cause rounding errors.
What about GetTextExtent functions? Do they need this too? Some test
cases would be nice.
--
Alexandre Julliard
julli...@winehq.org
On 3/25/2013 07:48, Dmitry Timoshkov wrote:
Why not just call GetParent() every time when a
notification is being sent?
Because it won't work if you create a control without WS_CHILD.
How is that different from the WM_WINDOWPOSCHANGING handler?
How what is different? There's a check for nu
On Mar 26, 2013, at 3:20 AM, Dmitry Timoshkov wrote:
> Ken Thomases wrote:
>
>> +ShowWindow( hwnd, SW_SHOW );
>> SetWindowLongPtrW( hwnd, GWLP_WNDPROC, (LONG_PTR)desktop_wnd_proc );
>> SendMessageW( hwnd, WM_SETICON, ICON_BIG, (LPARAM)LoadIconW( 0,
>> MAKEINTRESOURCEW(OI
Ken Thomases wrote:
> +ShowWindow( hwnd, SW_SHOW );
> SetWindowLongPtrW( hwnd, GWLP_WNDPROC, (LONG_PTR)desktop_wnd_proc );
> SendMessageW( hwnd, WM_SETICON, ICON_BIG, (LPARAM)LoadIconW( 0,
> MAKEINTRESOURCEW(OIC_WINLOGO)));
> if (name) set_desktop_window_title(
On Mar 8, 2013, at 6:20 AM,
wrote:
> I had a very annoying experience: when I started winemac the first
> time, the whole screen turned black for a fraction of a second. That
> was very unwelcome and reminded me of the infamous Intel-XOrg screen
> flickering issue that plagued many Linux distr
18 matches
Mail list logo
