August 2007 - Wine-Devel - list.winehq.org

Re: winmm: Change default driver order to be alsa,coreaudio,oss - try2

by Vitaliy Margolen

Maarten Lankhorst wrote: > Forgot to remove the strlen check. > Isn't this a bit premature? ALSA still does not support proper sound capture, working mixer, and not stable enough on some configurations. Vitaliy

Aug. 19, 2007

Re: Greek resource file for comctl final

by Paul Vriens

Dj Apal [GR] wrote: > OK changed the copyright and added the diff file for the rsrc.rc file so as > to be included. > > Thnx for noticing that! > > I think that we are OK now. Sorry for all this mess but it was my first time > posting a patch! > > > > ------------------------------------------------------------------------ > > Your 'greek_comctl' patch is in 'diff -up' format. The 'rsrc.diff' patch should also be in that format (and done from the root of your Wine source directory). Cheers, Paul.

Aug. 19, 2007

choppy anim

by Skrzynka

Hi, I'm trying to get some game (Settlers 3) to work on Wine (updated sources recently from git). If possible, I'd like to ask for some clues for a start: 1) the issue is choppy animation - the frame rate is abt 1/sec while the cpu load is low. However there are random periods when there seem to be about few frames per second (and cpu is laoded 100%). I tried measuring the time between call and return of DLL functions in relay.c. The only thing that looked suspiciously was WaitForSingle|MultipleObjects having times like 200-500ms. I also tried adding some delay to WaitForVerticalBlank in ddraw.c but also to no effect. Where should I start looking for the problem - some events or callbacks code? which? 2) when I run it from within winedbg i get lots of exceptions (no matter if app was started from winedbg or it was attached later) and no matter what combination of pass/continue I do, the app crashed with some msg box about exception or structured exception. Any pointers to docs on this? Any suggestions will help greatly. Thanks & regards Piotr -- ----- AlphaNet - najtaniej w sieci! -------- Odnowienia domen w rewelacyjnych cenach! .pl - 65 zl, .com.pl - 50 zl, reg - 20 zl http://www.domeny.alpha.pl --------------------------------------------

Aug. 18, 2007

Re: Direct3D 10 design considerations

by Stefan Dösinger

Am Samstag, 18. August 2007 19:59 schrieb Ivan Gyurdiev: > The shader stuff uses two different backends and an intermediate > interface (SHADER_OPCODE_ARG) to isolate the asm parser. Other parts of > wined3d could do the same thing - you are interface constrained from the > top (d3d) and from the bottom (gl), so it makes sense to focus on > intermediate representations of the data. If it's hard to replace your > GL backend, then the code isn't properly structured. > > ...and splitting things up is being considered yet again. > I'm not sure I like the idea of throwing away working code to start > "fresh" - but I'm no longer writing d3d code, so :) No question it is possible to keep things merged, but keep in mind that d3d10 throws away some things that are a major thing the current d3d->gl wrapping code is dealing with, like having sampler states device global. The step from d3d9 -> d3d10 is much bigger interface wise than d3d7(*) -> d3d8 or d3d8 -> d3d9 have been, it is so big that Microsoft decided to throw away their internal implementation and start over. This is why we discuss this. If Microsoft hadn't entirely changed the way d3d works internally there wouldn't be any reason for us to do the same too. D3D10 is a present. It is much closer to opengl than to d3d9. Having a common code means to deal with the overhead of mapping d3d9 to opengl in code that also runs d3d10. The question is how to deal with that overhead. (*) d3d7->d3d8 was a huge change too because it got rid of the ddraw stuff in d3d. However, the differences are initialization-wise only, rendering once the device is there works the same way in d3d7. d3d10 has a different "run-time" interface.

Aug. 18, 2007

Re: #winehq admin abuse

by Jan Zerebecki

On Thu, Aug 16, 2007 at 08:06:01PM -0700, Jonathan Challinger wrote: > I'm not going to continue this. This is my last message concerning this > argument. > I'm done with > wine, and now I'm done discussing its community's serious flaws. This is sad, after all a community is as good as the participants make it. > > On Thursday 16 August 2007 20:27:04 Jonathan Challinger wrote: > > > Jan Zerebecki, I'd be happy to help, but how? I could develop some > > > guidelines and rules for admins to follow, Though formulating proper communication guidelines is some work (one can borrow text and wisdom from projects that may have something like this; freenode, fedora, ubuntu, gentoo, debian come to mind), the real work is discussing it, asking everyone whose comments matter and getting everyone to agree. > > > but then what? How would they be enforced? Obviously then the people with the authority will support the needed enforcement. But IMHO the best atmosphere is when nobody needs to wield their powers. On Fri, Aug 17, 2007 at 08:06:25AM -0500, Jeremy White wrote: > he certainly should not be banned now. Done. In the future please don't discuss policy, rules or problems with ops/admins on #winehq but e.g. on #winehq-social ( unless we decide in the future that this is on-topic in #winehq ). > a ban is inappropriate except > in the most extreme cases, in my opinion. I think so, too. But others may have other opinions. As far as I understood Vitaliy Margolens position is that anyone who questions a admin/op should get banned. We have #winehq-social where anything can be discussed and nobody gets banned (unless they do advertisement or/and malware). Another problem is that we don't have a rule for when/how to unban. So if we could agree on rules for when and how to ban and unban, it would be a good start and our community should become a bit more pleasant. Jan

Aug. 18, 2007

Re: Greek resource file for comctl final

by Maarten Lankhorst

Dj Apal [GR] schreef: > > OK changed the copyright and added the diff file for the rsrc.rc file > so as to be included. > > Thnx for noticing that! > > I think that we are OK now. Sorry for all this mess but it was my > first time posting a patch! Just curious, are files supposed to have dos line terminators? It seems to me like your file has it. Cheers, Maarten

Aug. 18, 2007

Re: Direct3D 10 design considerations

by Ivan Gyurdiev

H. Verbeet wrote: > On 18/08/07, Roderick Colenbrander <thunderbird2k(a)gmx.net> wrote: > >> From what I have seen GL3 is very different. It would be like maintaining a >> GTK and a QT backend in one library. They use very different calls >> (glBegin/glEnable and so are gone), need different WGL contexts and so on. >> >> Sure in case of a wined3d-gl3 you'll end up fixing bugs twice. But for quite a >> number of bugs you'll need to patch both gl2 and gl3 anyway. >> >> > That's true, but there's also a rather large part of wined3d that's > not GL specific in the first place. The most obvious examples are most > of the shader stuff and state management, but that's certainly not > all. > The shader stuff uses two different backends and an intermediate interface (SHADER_OPCODE_ARG) to isolate the asm parser. Other parts of wined3d could do the same thing - you are interface constrained from the top (d3d) and from the bottom (gl), so it makes sense to focus on intermediate representations of the data. If it's hard to replace your GL backend, then the code isn't properly structured. It's interesting that all this work was done to move towards convergence: D3D1-9 -> Wined3d Pixelshaders, Vertexshader -> shared backend GLSL, ARB -> single shader parser ...and splitting things up is being considered yet again. I'm not sure I like the idea of throwing away working code to start "fresh" - but I'm no longer writing d3d code, so :)

Aug. 18, 2007

re: [patch] Garbage code in text string display

by Dan Kegel

Xin Guan wrote: > This patch solves the problem that many MBCS programs display garbage code > for text strings. Because most windows programmers do not handle charsets > properly, we have to force DEFAULT_CHARSET in here. Can you give a simple example of such a program (preferably downloadable)? Can you add a conformance test showing that your patch is correct? - Dan

Aug. 18, 2007

Re: Direct3D 10 design considerations

by Stefan Dösinger

Am Samstag, 18. August 2007 14:34 schrieb H. Verbeet: > > My suggestion would be to create a new wined3d with the same interface as > > the current wined3d. If needed ddraw/d3d8/d3d9 can use this wined3d too. > > Personally I would add d3d9ex.dll like on Vista which can use > > wined3d-gl3. > > I certainly wouldn't discard that option either. Keeping things > together, if possible, is just a slight preference. As for d3d9ex, it > appears to mostly be d3d9 with some extra flags in a couple of places. > I've got no idea if anyone is actually using it, or will be, but it > shouldn't be particularly hard to add. I am opposed to writing a 2nd wined3d with the same interface. One of the main problems, if we stay with one wined3d, is to map the d3d9 and d3d10 interface together efficiently(remember: Microsoft went for a new low level interface). If we use 2 wined3d's with the same interface we do not gain much compared to a common codebase(still two different implementations), but we still have the hassle of designing an internal interface that can run both d3d versions and is suitable for gl3 and very old gl 1.2 versions.

Aug. 18, 2007

Re: Greek resource patch for comctl [third attempt, last I hope!!]

by Paul Vriens

Dj Apal [GR] wrote: > Hope this is what u want us to send! ;) used --> diff -up /dev/null ... etc etc > > > > ------------------------------------------------------------------------ > > Hi, Just a few remarks. The copyright says 'Eric Kohl' is that correct? You also need to add this resource file to 'rsrc.rc' in that same directory otherwise it will never be picked up. Cheers, Paul.

Aug. 18, 2007