> <[EMAIL PROTECTED]> writes:
>
> > Which errors are you referring to? The most frequent ones
> > lately are the ones where the winetest package isn't
> > available on the sourceforge osdn mirror.
>
> For example this:
>
> > Winrash version: winrash-0008-chris-msvc.exe
> > [...]
> > winetest =
Which errors are you referring to? The most frequent ones lately are the ones where
the winetest package isn't available on the sourceforge osdn mirror. We are still
asking people to download the tests from this location for particular test releases.
I'd imagine the fix is simply to point the
No need to fork winehq to support such things. Imaging having to keep up with all of
the patches applied to the mainline code? It's probably better just to fix things
that break those apps in the winehq tree so every other app gets the benifit.
Chris
>
> From: Joel Konkle-Parker <[EMAIL PRO
I think we should switch the winrash id field from the users first and last name to an
email address we can contact the user at. There are a few odd errors that I'd like to
get more information about but its difficult to contact people via their first and
last name. Any objections to this? Wi
Lately I've been doing a lot of installer building with the NSIS
installer(http://nsis.sf.net). We could easily package winetest as a self-extracting
and executing installer that was transparent to the user. The installer would simply
extract the actual winetest.exe to windows/temp, start it u
>like "play this wave file". The major remaining drawback >is latency;
>click on button in app, hear sound 2 seconds later when >scheduler
This is why we have sound servers like jack. Any delay is likely due to not having a
fully callback based architecture in the app.
>Maybe a better thing to
Any idea when the kernel and wine changes will be going in? Then we can start asking
people with Fedora to disable exec-shield and prelinking OR upgrade to kernel 2.6.X
and the latest wine. There are people everyday that come onto #winehq with problems
due to prelinking/exec-shield.
Thanks,
C
Yes, my bad. I'll send in a fixed patch. I still don't like the way the code looks
with the duplication of the default string to use but I couldn't think of any way to
fix it more elegantly. Ideas?
Chris
>
> From: Mike Hearn <[EMAIL PROTECTED]>
> Date: 2004/03/29 Mon AM 06:07:03 EST
> To:
I've been working to debug one users problem with an i810 card. (n wodOpen() we try
to set the format of the audio, 16 or 8bit. I believe the i810 only supports 16bit so
we return MMSYS_ERR. I *think* we should be returning WAVERR_BADFORMAT instead so
wine can try another format that may work
Can you add me as a maintainer of the appdb as well? I'm often helping people in irc
so I deal a lot with people trying to run all kinds of different apps, would be useful
to start filling in some information on them so we have some kind of record of how
well they run under wine.
Thanks,
Chris
Yes, I too think we need to support the appdb.
Perhaps we should setup some kind of application submission interface where users can
fill things in and provide links to screen captures and such. Maintainers could then
go through and apply the changes to the db and copy the images to a local loc
What is the plan for combining these audio drivers? One thing that is common to each
driver are the functions that handle the wave headers, adding, removing etc.
I'm also weary of any kind of combination that includes OSS as OSS is depreciated and
has been replaced by Alsa.
I'm also concerned
Without a test how can you know if this implementation produces the correct values?
What about variant type conversions? It seems silly to send a patch without testing
it...
Chris
>
> From: Fabian Cenedese <[EMAIL PROTECTED]>
> Date: 2004/02/19 Thu AM 08:20:21 EST
> To: [EMAIL PROTECTED]
>
I like it. Much easier for users to find the correct downloads than it was with the
previous pages sourceforge image/link.
Chris
>
> From: "Dimitrie O. Paun" <[EMAIL PROTECTED]>
> Date: 2004/02/17 Tue AM 02:34:11 EST
> To: Wine Devel <[EMAIL PROTECTED]>
> CC: [EMAIL PROTECTED], Chris Morgan
> On February 4, 2004 05:20 pm, [EMAIL PROTECTED] wrote:
> > I'm pretty sure lots of other wine code uses 2 space indents, I know I
> > started using them after working with wine.
>
> Yes, other code does so, but I think the preferred style is 4-space.
> Now, as I said, if you feel strongly abou
I'm pretty sure lots of other wine code uses 2 space indents, I know I started using
them after working with wine.
No other comments on the ui changes in winecfg? ;-) I'll submit to wine-patches
tonight after going through the code once more.
The x11 tab is global settings only at this point
Well documentation/documentation.sgml 1.12->1.13 was when the change was made in cvs,
and that looks like it was 3+ months ago.
Chris
>
> From: Jeremy Newman <[EMAIL PROTECTED]>
> Date: 2004/01/19 Mon AM 10:52:47 EST
> To: Chris Morgan <[EMAIL PROTECTED]>
> CC: [EMAIL PROTECTED]
> Subject: Re:
If other people think it makes sense then yes, I think we should probably move the
autodetection code to run at wine startup. The code thus far is very much
non-portable so while it should work under linux I'm not sure about other os's. I've
considered also trying to dynamically load the sound
Ahh yes, this appears to be the issue. If I go to "project
settings->link->object/library modules" and add "uuid.lib" to the list then the test
compiles without many other issues. Shouldn't the script be adding this to the
.dsp/.dsw?
I'm having great troubles compiling the test against vs6 he
> > (4b) wodPlayer_FeedDSP()
> >
> > In the while loop, I could not figure out the purpose of 'availInQ >
> > SPACE_THRESHOLD', so I changed it to 'availInQ'. In reality, the
> > SPACE_THRESHOLD check could probably be left in, I am not sure what
> > the purpose was in the first place.
> Dunno eit
If we also had working defaults for the users cdrom drive(s) and floppy drive then
this would work quite well. Many users will want to install applications from cdrom.
We could autodetect this at startup.
Chris
>
> From: "Dimitrie O. Paun" <[EMAIL PROTECTED]>
> Date: 2004/01/06 Tue AM 09:4
How do we plan to get rid of having default config files? Where would the default
registry go?
Chris
>
> From: Alexandre Julliard <[EMAIL PROTECTED]>
> Date: 2004/01/05 Mon PM 03:19:54 EST
> To: Chris Morgan <[EMAIL PROTECTED]>
> CC: [EMAIL PROTECTED]
> Subject: Re: install default config fi
Registering the dlls? Is this the same as loading them?
How would we know which dll was responsible for creating which registry entries? Is
it that clear which one should do it?
Would the code called during registration check to see if the default keys existed and
if it didn't install the def
23 matches
Mail list logo
