January 2006 - Wine-Devel - list.winehq.org

New developer

by Segin

Hello! I am new to developing Wine, however, I am not new to using it (I know quite a bit about it already). I want to know what resources would I want to look at, please nothing obvious (bugzilla, MSDN, etc.), and what I can do to contribute. Thanks.

Jan. 31, 2006

Re: dx9 and shaders

by Roderick Colenbrander

> Is there a TODO or similar documentation on D3D8 & 9 for Wine? I don't > necessarily have much background in DirectX. Last time I used it was > when DirectX 3.0 was brand spanking new and was all the rave. I'm > willing to work, but don't know where to start and am limited on time > available to search for it. If someone has already begun some > organization of this, like a hit-list or something, that would be quite > helpful. > There's no todo list right now. Right now the best approach would be to finish the d3d8 to wined3d move so that both d3d8 and d3d9 share the same core. Then remaining bugs should be fixed so that more games work. After that performance tweaks should be added and more features like shaders. > Also, does anybody know what the status is compared to WineX/Cedega? Do > they have a more fully featured shader implementation? What's there > status/policy on porting back to Wine? A long time ago WineX/Cedega separated from Wine. In the beginning when Wine was X11 licensed they sometimes ported stuff back to Wine but these days they don't do that anymore. Wine's implementation of Direct3D is quite good but compared to cedega performance isn't optimal and our shader support is very basic but modern games like Halflife2 and others work. Roderick

Jan. 31, 2006

Re: dx9 and shaders

by Coleman Kane

On Tue, 2006-01-31 at 21:26 +0100, Roderick Colenbrander wrote: > There's some initial shader stuff in wine but not sure how well it works. I > don't know what the status on it is as we haven't heard anything from the guy > who was working on this. He was also working on moving the d3d8 code over to > wined3d. If you have time to help out, all help is usefull :) > One of the usefull things to do before starting to hack on shaders is to > finish the d3d8/d3d9 merge as both can then share the same shader code. > > Roderick > > > On Tuesday 31 January 2006 20:37, Coleman Kane wrote: > > Hi, > > > > What is the status on Shader support for DX9 in the latest WINE cvs, and > > the future projections of support in this area? > > > > I am working on a transition project, and am curious how far off support > > for this is in the WINE project, and perhaps where work needs to be > > done. Are there any people organizing this effort here? > > > > -- > > Coleman Kane Is there a TODO or similar documentation on D3D8 & 9 for Wine? I don't necessarily have much background in DirectX. Last time I used it was when DirectX 3.0 was brand spanking new and was all the rave. I'm willing to work, but don't know where to start and am limited on time available to search for it. If someone has already begun some organization of this, like a hit-list or something, that would be quite helpful. Also, does anybody know what the status is compared to WineX/Cedega? Do they have a more fully featured shader implementation? What's there status/policy on porting back to Wine? Any work that I do will fall right back in the Wine repo. -- Coleman Kane

Jan. 31, 2006

Re: dx9 and shaders

by Roderick Colenbrander

There's some initial shader stuff in wine but not sure how well it works. I don't know what the status on it is as we haven't heard anything from the guy who was working on this. He was also working on moving the d3d8 code over to wined3d. If you have time to help out, all help is usefull :) One of the usefull things to do before starting to hack on shaders is to finish the d3d8/d3d9 merge as both can then share the same shader code. Roderick On Tuesday 31 January 2006 20:37, Coleman Kane wrote: > Hi, > > What is the status on Shader support for DX9 in the latest WINE cvs, and > the future projections of support in this area? > > I am working on a transition project, and am curious how far off support > for this is in the WINE project, and perhaps where work needs to be > done. Are there any people organizing this effort here? > > -- > Coleman Kane

Jan. 31, 2006

dx9 and shaders

by Coleman Kane

Hi, What is the status on Shader support for DX9 in the latest WINE cvs, and the future projections of support in this area? I am working on a transition project, and am curious how far off support for this is in the WINE project, and perhaps where work needs to be done. Are there any people organizing this effort here? -- Coleman Kane

Jan. 31, 2006

Re: opengl: Sync a dibsection to its pixmap before drawing to it via opengl

by Huw D M Davies

On Sun, Jan 29, 2006 at 07:45:39PM +0100, Lionel Ulmer wrote: > On Fri, Jan 27, 2006 at 03:48:00PM +0000, Huw D M Davies wrote: > > Huw Davies <huw(a)codeweavers.com> > > opengl: Sync a dibsection to its pixmap before drawing to it via opengl > > Was some benchmarks done to see if this change negatively impacted the > performance of applications doing only 'in-window' drawings (e.g. games) and > not 'in-dib' drawings ? In a word, 'no'. However it shouldn't be too bad, the 'in-window' path calls glXGetCurrentContext, get_context_from_GLXContext and GetObjectType. The first and last of these should be quick, as should the second unless there are loads of contexts floating about. Huw.

Jan. 31, 2006

Wine and Font rendering

by Roland Kaeser

Hello all I noticed a very strange font problem in Corel Draw using wine. On some systems (all SuSE 10) rotated fonts became invisible. An other problem is with text boxes on some systems text boxes (with floating text) are very strange rendered (the text appears multiple times, the cursor is not at the position where the character is printed while writing, some text is invisible while editing) Can somebody tell me which routines (system and wine) are responsible for font rendering in wine. Based on that all machines have the same graphics card and driver version, I'm pretty sure its not a driver or graphics card related problem but on some systems, online updates are made. If I could know about the internal work of font rendering in wine, I probably can figure out where this problem cames from. Many thanks Roland Kaeser

Jan. 31, 2006

Re: linux/capi.h: present but cannot be compiled

by Marcus Meissner

On Tue, Jan 31, 2006 at 10:57:52PM +1100, Joshua Crawford wrote: > (I'm not on the devel list, so please Cc: replies either to me or the users > list.) > > After recently upgrading my distro (from Slackware 10.1 to Slackware 10.2 > with Freerock GNOME), configure (current CVS) now reports It will likely work nethertheless, see here: > configure: WARNING: linux/capi.h: present but cannot be compiled > configure: WARNING: linux/capi.h: check for missing prerequisite headers? > configure: WARNING: linux/capi.h: see the Autoconf documentation > configure: WARNING: linux/capi.h: section "Present But Cannot Be Compiled" > configure: WARNING: linux/capi.h: proceeding with the preprocessor's result > configure: WARNING: linux/capi.h: in the future, the compiler will take precedence ... > configure:7252: WARNING: linux/capi.h: present but cannot be compiled > configure:7254: WARNING: linux/capi.h: check for missing prerequisite headers? > configure:7256: WARNING: linux/capi.h: see the Autoconf documentation > configure:7258: WARNING: linux/capi.h: section "Present But Cannot Be Compiled" > configure:7260: WARNING: linux/capi.h: proceeding with the preprocessor's result > configure:7262: WARNING: linux/capi.h: in the future, the compiler will take precedence > configure:7274: checking for linux/capi.h > configure:7281: result: yes Ciao, Marcus

Jan. 31, 2006

Re: keyboard: fix the keyboard problem when using UTF-8 locales

by Dmitry Timoshkov

On Tue, 2006-01-31 at 14:36 +0000, Robert Shearman wrote: > Then how should Fatih's problem be fixed? I don't know. It works here just fine for ru_RU.UTF-8 and XLookupString apparently doesn't return UTF-8 encoded strings on keyboard detection, X11 sends UTF-8 encoded characters with KeyPress events though. -- Dmitry.

Jan. 31, 2006

Re: user: fix DrawTextExA/W on empty strings.

by Rein Klazes

On Fri, 27 Jan 2006 10:28:04 -0800, you wrote: >(Apart from the other discussion) are you sure that you really >mean that? >"If the length is explicitly stated to be zero then don't do the >calcrect but if the length is to be measured and happens to come >out as zero then do do the calcrect" >If so then I suggest at least a comment that it is deliberate; it >sounds counterintuitive to me. I thought I did even better by providing tests for each of those cases, which pass here under Win2k and XP. Other weird observations: the different behavior of the A and W functions; the "return 0" in that code are actually "return 1" on Win2k but not on XP. Rein.

Jan. 31, 2006