On Sun, Apr 27, 2008 at 5:04 AM, Eric Pouech <[EMAIL PROTECTED]> wrote:
> James Hawkins a écrit :
>
>
> > Hi,
> >
> > Changelog
> > * Remove two tests that fail on all platforms.
> >
> > dlls/msvcrt/tests/cpp.c |2 --
> > 1 files changed, 0 insertions(+), 2 deletions(-)
> >
> >
> > --
Dan Hipschman wrote:
> On Sat, Apr 26, 2008 at 09:51:58AM +0100, Robert Shearman wrote:
>
>> +u_suffix(l|L)
>> +l_suffix(u|U)
>>
>
> I'm guessing you meant for these to be the other way around.
>
Good spot, thanks!
--
Rob Shearman
Am Sonntag, 27. April 2008 21:21:22 schrieb Vitaliy Margolen:
> Vitaliy Margolen wrote:
> > As discussed in bug 11584 this Preload is wrong and should be removed.
> > ---
> > dlls/wined3d/context.c |7 ---
> > 1 files changed, 0 insertions(+), 7 deletions(-)
This patch almost certainly cor
Roderick Colenbrander wrote:
> Maarten wrote:
>> A lot of the lowest level stuff is currently missing. If you don't
>> mind x64 assembly it's not impossible to do. We would need support
>> from gcc for the windows calling convention, and making it possible to
>> mix linux calling convention with wi
> Vitaliy Margolen wrote:
> > As discussed in bug 11584 this Preload is wrong and should be removed.
> > ---
> > dlls/wined3d/context.c |7 ---
> > 1 files changed, 0 insertions(+), 7 deletions(-)
> >
> >
> BTW this is still not enough to fix all the problems. There are few more
> prelo
Vitaliy Margolen wrote:
> As discussed in bug 11584 this Preload is wrong and should be removed.
> ---
> dlls/wined3d/context.c |7 ---
> 1 files changed, 0 insertions(+), 7 deletions(-)
>
>
BTW this is still not enough to fix all the problems. There are few more
preloads that make Psyc
Christoph Frick wrote:
> Add dinput support for BSD's usbhid joysticks
>
> + if (have_joy_devs == 0) {
> + joy_devs = HeapAlloc(GetProcessHeap(), HEAP_ZERO_MEMORY,
> sizeof(struct JoyDev));
> + } else {
> + HeapReAlloc(GetProcessHeap(), 0, joy_devs, (1 + have_joy_devs) *
On Sun, Apr 27, 2008 at 7:58 AM, Tijl Coosemans <[EMAIL PROTECTED]> wrote:
> >> The only time Wine should have to worry about DPI is when running
> >> apps that haven't been designed with high DPI in mind and therefore
> >> don't scale well (for instance when font sizes are set in points and
>
On Sunday 27 April 2008 14:43:32 Dmitry Timoshkov wrote:
> "Tijl Coosemans" <[EMAIL PROTECTED]> wrote:
>> If users want a graphical way of setting physical display size, then
>> that's a job for the desktop environments to provide some tools to
>> configure the local X server.
>
> Same applies to
Dmitry Timoshkov <[EMAIL PROTECTED]> wrote:
> How about doing what Windows does - add a font preview to allow the user
> to see an actual size of the font he/she will get after the change?
Yeah, that would be great. We did something like that
in the Picasa for Linux font settings tool. Nigel s
"Tijl Coosemans" <[EMAIL PROTECTED]> wrote:
> If users want a graphical way of setting physical display size, then
> that's a job for the desktop environments to provide some tools to
> configure the local X server.
Same applies to many other settings like fonts and colors. Wine uses
the DPI sett
On Sat, Apr 26, 2008 at 11:37 PM, Steven Edwards <[EMAIL PROTECTED]> wrote:
>> * have start.exe set an environment variable saying "show
graphical error box
>> on dll load failure", and clear that before calling executed apps' WinMain()
>
> So that worked. Comments are welcome!
1. I'd output th
On Sun, Apr 27, 2008 at 10:22 PM, Dmitry Timoshkov
<[EMAIL PROTECTED]> wrote:
> "Jeff Zaroyko" <[EMAIL PROTECTED]> wrote:
>
>
> > system.ini, drivers32,,"vidc.MRLE=msrle32.dll" -system.ini,
> drivers32,,"vidc.MSVC=msvidc32.dll" +system.ini,
> drivers32,,"vidc.msvc=msvidc32.dll" system.ini,
> driv
"Jeff Zaroyko" <[EMAIL PROTECTED]> wrote:
> system.ini, drivers32,,"vidc.MRLE=msrle32.dll"
> -system.ini, drivers32,,"vidc.MSVC=msvidc32.dll"
> +system.ini, drivers32,,"vidc.msvc=msvidc32.dll"
> system.ini, drivers32,,"vidc.CVID=iccvid.dll"
> system.ini, drivers32,,"; vidc.IV50=ir50_32.dll"
> "Dan Kegel" <[EMAIL PROTECTED]> wrote:
>> On Sat, Apr 26, 2008 at 7:54 PM, L. Rahyen <[EMAIL PROTECTED]> wrote:
>>> 200 DPI limit is acceptable for most users. However, what this patch
>>> done by setting maximum to this small value (144) doesn't seems to
>>> be acceptable.
>>
>> Users really ar
"Dan Kegel" <[EMAIL PROTECTED]> wrote:
> On Sat, Apr 26, 2008 at 7:54 PM, L. Rahyen <[EMAIL PROTECTED]> wrote:
>> 200 DPI limit is acceptable for most users. However, what this patch
>> done by
>> setting maximum to this small value (144) doesn't seems to be acceptable.
>
> Users really
James Hawkins a écrit :
> Hi,
>
> Changelog
> * Remove two tests that fail on all platforms.
>
> dlls/msvcrt/tests/cpp.c |2 --
> 1 files changed, 0 insertions(+), 2 deletions(-)
>
>
>
>
>
the first one is actually bog
17 matches
Mail list logo