I'd have to agree with you guys on this one. One thing I can think of
that I would like to take on (given enough time to do it all) is create
a wiki page that I can use to document all of the fixme's, warn's and
err's that occur in the source, and then ask anyone that is contributing
code to u
On Wednesday 15 June 2005 10:10 pm, Jeremy White wrote:
> The rc of -16 is EBUSY.
>
> To be honest, I find it odd that you're getting
> a success while the sound card is in use; in
> my testing, any attempt to open a pcm that is
> in use generates a -16 return code, whether it
> be default:0 or pl
Getting closer, I had to change
+/*
+** See if it's a valid playback device
+**--*/
+if (ALSA_TestDeviceForWine(card, device
Brian Vincent wrote:
A few weeks ago Ivan asked me about getting him a VMWare Workstation
license. I contacted VMWare and they graciously donated 5 licenses to
Wine. I thought that was pretty generous of them.
It was very generous, it's already proven very useful (See ioctl patch, more
are
Hi,
Is MXSML working properly at the moment?
I've been trying to get render monkey working so I can
do some more testing on vertex shaders but if fails
with the following error:
XML Parse Error:
FIle: data\rm_registry.rfx
Error Code -2147024891
Reason: System error -2147024891
Line Nunmber: 0
L
On Tuesday 14 June 2005 11:21 pm, Jeremy White wrote:
> Kevin Koltzau wrote:
> Actually, try this one instead. Turns out that if
> you open a device with default:0 on some versions
> of alsalib (my laptop, as opposed to my work box),
> then snd_pcm_name() fails. Sigh.
Getting closer, I had to ch
Hi,
On Thursday 16 June 2005 01:15, [EMAIL PROTECTED] wrote:
> Hey , and it looks to be working nicely , damn you ;)
Thanks to your wine config and .dlls and whatever made the change. Do be
analyzed later ...
> You just have to resist sending everyone three page emails now!
I can imagine - es
Will the recent d3d patches by Oliver be committed?
Thanks
Joerg
--
Joerg Mayer <[EMAIL PROTECTED]>
We are stuck with technology when what we really want is just stuff that
works. Some say that should read Microsoft instead of technology.
I'm trying to install Visual C++.net and it is quiting without error.
The paths look strange in this trace.
WINEDEBUG=+file wine /mnt/cdrom1/setup.exe
trace:file:CreateFileW L".\\C:" QUERY_ACCESS creation 3 attributes 0x0
trace:file:RtlDosPathNameToNtPathName_U (L".\\C:",0xbfffe4a8,(ni
Hey , and it looks to be working nicely , damn you ;)
You just have to resist sending everyone three page emails now!
I got one step nearer by moving from 20050310-r1 to 20050524 . This
enabled wine to correctly adjust the volume settings and got me through
the basic audio setup of NS7.
Al
--- André Carvalho <[EMAIL PROTECTED]> wrote:
> I posted the same message on wine-user list , but
> got no help.
>
> Hi,
>
> I was wondering if someone could help me on this
> issue.
>
> I use a windows program that print direct to the
> printer, but it uses
> the printer from the printer li
MSN Messenger 6.2 (!!) seems to run fairly well with only builtin dll's,
from what I can tell the only real thing missing is CreateTextServices
in riched20.dll, SSL support and urlmon's obtainuseragent (or
something), webcams will work without any additional native dll now, if
my patch for msvfw32
Ideally, I don't think we want to link to libavcodec at all. We should
import code for as many filters as native implements, without stepping
on patented territory.
How would you benefit from ffmpeg update in a seamlessly manner?
Note that some months ago, I did a version of the wrapper
--- Phil Krylov <[EMAIL PROTECTED]> wrote:
> this change gives me a lot of errors when compiling:
> encode.o(.text+0x3b): In function `test_encodeInt':
> /home/phil/build/wine/dlls/crypt32/tests/encode.c:74: undefined
> reference to
> `CryptEncodeObjectEx'
Works for me here. CryptEncodeObjectEx i
Hi,
this change gives me a lot of errors when compiling:
make[3]: Entering directory `/home/phil/build/wine/dlls/crypt32/tests'
../../../tools/winegcc/winegcc -B../../../tools/winebuild -mconsole
encode.o main.o protectdata.o testlist.o -o crypt32_test.exe.so -L../../../
libs/port -lwine_port -L
Huw D M Davies wrote:
Huw Davies <[EMAIL PROTECTED]>
For modal propsheets we should run our own message loop rather than
use a modal dialogbox just like Windows does. This helps apps that
subclass the propsheet's wndproc.
+static INT do_loop(PropSheetInfo *psIn
On Wed, 2005-06-15 at 13:25 +0200, Alexandre Julliard wrote:
> Yes, but it doesn't really help if the comments are not up to
> date. I'd prefer to make sure it's dead easy to update the doc
> directly rather than ask people to maintain comments and then have to
> come back and sync with the doc. Th
Dimi Paun <[EMAIL PROTECTED]> writes:
> Well, it's not a matter of building the docs only by grepping, that
> wouldn't be feasible. But _checking_ if anything has been added or
> deleted can be done easily. And that would be the important trigger for
> someone to go in and update the documentation
On Wed, 2005-06-15 at 10:51 +0200, Alexandre Julliard wrote:
> It's not the extra work, it's that I'm not convinced we want to add a
> lot of noise in the source for that. I don't think we can
> realistically hope to build the documentation only by grepping, we
> need to check the source anyway.
W
"Dmitry Timoshkov" <[EMAIL PROTECTED]> writes:
> "Alexandre Julliard" <[EMAIL PROTECTED]> wrote:
>
> > This isn't correct, the size is 2 only for standalone tests.
>
> The case above is protected by #ifdef STANDALONE so that shouldn't be an
> issue.
testlist.c defines STANDALONE too (yes it's
"Dimi Paun" <[EMAIL PROTECTED]> writes:
> Yeah, agreed. But it would be so much easier to keep the docs
> up-to-date if we can simply grep for the values. I'm not
> suggesting that you do the work, but if you think we can mark
> them somehow for easy grepping, we can add it as a Janitorial
> task.
21 matches
Mail list logo
