On Mon, Nov 9, 2009 at 12:47 AM, Dan Kegel wrote:
> Jerome Leclanche wrote:
>> Austin English wrote:
>>> Anyone opposed to removing that keyword?
>>
>> +1 on removing it.
>> It would be nice to have a bugzilla filter to replace it, too.
>>
>> Are we keeping "tasklist" and "tasklet" keywords as we
Le 9 avril 2010 13:30, Frédéric Delanoy a écrit :
> 2010/4/9 Nicolas Le Cam :
>> Hi Frédéric,
>>
>>>+processus clients se sont terminés. Ceci évite le coût inhérent à l'arrêt
>> sont -> soient
>>
>>>+\fIwineserver\fR dans le chemin système ou quelques autres emplacements
>>>vraisemblables.
>> "po
Le 9 avril 2010 13:23, Frédéric Delanoy a écrit :
> Well I thought about putting it in non-infinitive form, but it didn't
> sound/feel right to me.
>
> In fact "N'affiche" would be more like a description, while
> "N'afficher" is more an action/modifier/behaviour "alterator"
> which seems the purp
Le 9 avril 2010 13:37, Frédéric Delanoy a écrit :
> 2010/4/9 Nicolas Le Cam :
>> Hi Frédéric,
>>
>>>+\fIwineserver\fR dans le chemin système ou quelques autres emplacements
>>>vraisemblables.
>>>[...]
>>>+"wine" dans le chemin système ou quelques autres emplacements
>>>vraisemblables.
>> Even if
On Thu, Apr 8, 2010 at 8:29 PM, Alexandre Julliard wrote:
> Mike Kaplinskiy writes:
>
>> This won't work for implementing half-closed sockets. If we have only
>> the read half is closed, we will get POLLIN/0 recv indefinitely if we
>> keep polling (not POLLHUP). If we remove it from the loop, we
On Fri, 2010-04-09 at 15:50 +0200, wy...@volny.cz wrote:
> Hi, this will be just a short note... I noticed some new icons and i
> like them!
>
> W.
>
There's plenty more to come: http://www.airwebreathe.org.uk/wine-icon/ !
On Fri, Apr 9, 2010 at 12:50 PM, Dan Kegel wrote:
> On Fri, Apr 9, 2010 at 10:44 AM, Roderick Colenbrander
> wrote:
>> Just something else which is a little related. Does winetricks handle
>> SysWow64 already?
>
> Nope. Waiting for the first bug report or first patch...
There actually is a bug
On Fri, Apr 9, 2010 at 10:44 AM, Roderick Colenbrander
wrote:
> Just something else which is a little related. Does winetricks handle
> SysWow64 already?
Nope. Waiting for the first bug report or first patch...
On Fri, Apr 9, 2010 at 7:30 PM, Dan Kegel wrote:
> Helge wrote:
>> I happen to have Windows/System32.
>
> Hang on right there. Why? Once I understand that, the rest will be easier.
>
> Winetricks does handle the case where users renamed windows/fonts to
> windows/Fonts, because it was observed
Helge wrote:
> I happen to have Windows/System32.
Hang on right there. Why? Once I understand that, the rest will be easier.
Winetricks does handle the case where users renamed windows/fonts to
windows/Fonts, because it was observed happening in the wild
(one can imagine users doing thiis when
Helge Hafting wrote:
> I just tried installing gdiplus using winetricks, on a debian testing
> system.
>
> This failed, as winetricks tried to copy stuff into windows/system32,
> where I happen to have Windows/System32.
As usual start with a clean Wine prefix 'rm -rf ~/.wine', and try again.
On Fri, Apr 9, 2010 at 8:45 AM, Helge Hafting wrote:
> I just tried installing gdiplus using winetricks, on a debian testing
> system.
>
> This failed, as winetricks tried to copy stuff into windows/system32,
> where I happen to have Windows/System32.
>
> I first tried making symlinks windows->Win
Hi, this will be just a short note... I noticed some new icons and i
like them!
W.
I just tried installing gdiplus using winetricks, on a debian testing
system.
This failed, as winetricks tried to copy stuff into windows/system32,
where I happen to have Windows/System32.
I first tried making symlinks windows->Windows and system32->System32.
winetricks would run, but the app u
André Hentschel wrote:
> +#define TESTMARKER(w) \
> +markerW[2] = w; \
> +ok(!lstrcmpW(markerW,nomarkerW), "expected the character 0x%x to be
> ignored within the string\n", w);
> +
> +static void test_lstrcmpW(void)
> +{
> +static const WCHAR nomarkerW[] = {'t','e','s','t',0
On 8 April 2010 22:49, Roderick Colenbrander wrote:
> + /* Source and/or destination need to be on the GL side */
> + if (src_pool == WINED3DPOOL_SYSTEMMEM || dst_pool ==
> WINED3DPOOL_SYSTEMMEM)
> + return FALSE;
...
> + if (!is_identity_fixup(src_format_desc->color_fixup) ||
> +
On 04/09/2010 01:12 PM, André Hentschel wrote:
+#define TESTMARKER(w) \
+markerW[2] = w; \
+ok(!lstrcmpW(markerW,nomarkerW), "expected the character 0x%x to be ignored
within the string\n", w);
Hi André,
lstrcmpW is not implemented on Win95/98/Me so these tests will always
su
2010/4/9 Nicolas Le Cam :
> Hi Frédéric,
>
>>+processus clients se sont terminés. Ceci évite le coût inhérent à l'arrêt
> sont -> soient
>
>>+\fIwineserver\fR dans le chemin système ou quelques autres emplacements
>>vraisemblables.
> "potentiels" or "possibles" suit better.
>
My understanding was
Well I thought about putting it in non-infinitive form, but it didn't
sound/feel right to me.
In fact "N'affiche" would be more like a description, while
"N'afficher" is more an action/modifier/behaviour "alterator"
which seems the purpose of an command-line option IMHO.
Frédéric
On Fri, Apr 9,
> Message du 09/04/10 11:33
> De : "Alexandre Julliard"
> A : "Christian Costa"
> Copie à : wine-devel@winehq.org
> Objet : Re: [PATCH] d3dx9_36: Beginning of constants parsing + tests (based
> on work from Luis Busquets) (try 3) (resend)
>
>
> Christian Costa writes:
>
> > @@ -650,6 +650,29
On Fri, Apr 9, 2010 at 12:40 PM, Ben Klein wrote:
> On 9 April 2010 20:30, Damjan Jovanovic wrote:
>> On Fri, Apr 9, 2010 at 12:04 PM, Dan Kegel wrote:
>>> This seemed like a useful overview of how the various layers relate to
>>> each other:
>>> http://tuxradar.com/content/how-it-works-linux-au
On 9 April 2010 20:30, Damjan Jovanovic wrote:
> On Fri, Apr 9, 2010 at 12:04 PM, Dan Kegel wrote:
>> This seemed like a useful overview of how the various layers relate to
>> each other:
>> http://tuxradar.com/content/how-it-works-linux-audio-explained
>>
>>
>>
>
> http://insanecoding.blogspot.c
On Fri, Apr 9, 2010 at 12:04 PM, Dan Kegel wrote:
> This seemed like a useful overview of how the various layers relate to
> each other:
> http://tuxradar.com/content/how-it-works-linux-audio-explained
>
>
>
http://insanecoding.blogspot.com/2009/06/state-of-sound-in-linux-not-so-sorry.html
is ano
On 9 April 2010 11:04, Dan Kegel wrote:
> This seemed like a useful overview of how the various layers relate to
> each other:
> http://tuxradar.com/content/how-it-works-linux-audio-explained
This is somewhat confusing:
* PulseAudio is an audio mixer that provides a finer grained control
over v
On 9 April 2010 20:04, Dan Kegel wrote:
> This seemed like a useful overview of how the various layers relate to
> each other:
> http://tuxradar.com/content/how-it-works-linux-audio-explained
A cursory glance does not reveal any mention of libalsa as a valid
"sound input", and I'm not sure but I
This seemed like a useful overview of how the various layers relate to
each other:
http://tuxradar.com/content/how-it-works-linux-audio-explained
André Hentschel writes:
> @@ -617,6 +617,12 @@ static void test_UrlGetPart(void)
>dwSize = sizeof szPart;
>szPart[0]='x'; szPart[1]=0;
>res = pUrlGetPartA("hi", szPart, &dwSize, URL_PART_SCHEME, 0);
> +
> + if (res) {
> +win_skip("probably too old IE\n");
> +return;
> + }
T
André Hentschel writes:
> @@ -7708,7 +7708,7 @@ HRESULT WINAPI VarDateFromStr(OLECHAR* strIn, LCID
> lcid, ULONG dwFlags, DATE* pd
>break;
>
> case 0x1B: /* localized DDDTTT */
> - if (!iDate)
> + if (PRIMARYLANGID(lcid) != LANG_GERMAN)
Obviously you cannot hardcode spe
Christian Costa writes:
> @@ -650,6 +650,29 @@ HRESULT WINAPI D3DXCompileShader(LPCSTR pSrcData,
> return D3DERR_INVALIDCALL;
> }
>
> +typedef struct ctab_constant ctab_constant;
> +
> +struct ctab_constant {
> +D3DXCONSTANT_DESC desc;
> +ctab_constant* members;
> +};
> +
> +inlin
On 07/04/10 06:39, Dan Kegel wrote:
winedbg's bt all seems broken since sometime between 1.1.40 and now.
Has anybody else seen this?
If I start a program under debugger control with "./wine winedbg
~/test/my.exe" then I see errors such as "Can't get context for thread
0021 in current proc
Hi Frédéric,
>+N'afficher aucun message de statut.
It doesn't really matter but as you don't use infinitive form
elsewhere perhaps "N'affiche" could be better.
Thanks again for your work.
--
Nicolas Le Cam
Hi Frédéric,
>+processus clients se sont terminés. Ceci évite le coût inhérent à l'arrêt
sont -> soient
>+\fIwineserver\fR dans le chemin système ou quelques autres emplacements
>vraisemblables.
"potentiels" or "possibles" suit better.
--
Nicolas Le Cam
Hi Frédéric,
>+\fIwineserver\fR dans le chemin système ou quelques autres emplacements
>vraisemblables.
>[...]
>+"wine" dans le chemin système ou quelques autres emplacements vraisemblables.
Even if "likely" literally means "vraisemblable" I think the previous
use of "potentiel" or even "possible
33 matches
Mail list logo
