wine-devel April 2007

wine-devel@winehq.org

139 participants
312 discussions

Re: [2/2] wined3d: Only issue state_patchsegments FIXME once.
by H. Verbeet 04 Apr '07

04 Apr '07

On 03/04/07, Felix Nawothnig <flexo(a)holycrap.org> wrote: > This really kills performance in upcoming Soldat 1.4 (looks like they > set this to bogus values even more often now). > --- Nothing against this change, but in general when playing games you should be running with WINEDEBUG="-all".

1 0

Start Menu handle?
by Indira Muthuswamy 04 Apr '07

04 Apr '07

Hai, How do I get handle to start menu in a handheld device? Thanks and Regards, M.Indu

1 0

Re: pathc for printdlg.c
by Dmitry Timoshkov 04 Apr '07

04 Apr '07

"Ivan Sinitsin" <ivan(a)etersoft.ru> wrote: > This patch corrects background color of a dialogue window "Print Dialog ". For > background color of dialog windows it used the background color of class > DIALOG or the COLOR_BTNFACE. > + case WM_CTLCOLORDLG: > + hbr=(HBRUSH)GetClassLongPtrW( hDlg, GCLP_HBRBACKGROUND); > + if (!hbr) hbr=(HBRUSH)GetSysColorBrush(COLOR_BTNFACE); > + return hbr; Why do you need this? Def[Wnd|Dlg]Proc is supposed to handle that. -- Dmitry.

1 0

Re: Propsheet exception fix
by Joris Huizer 03 Apr '07

03 Apr '07

--- Aric Stewart <aric(a)codeweavers.com> wrote: > Do not attempt to draw a page during WM_PAINT if > there is no active page. > Test which shows this working, causes exception > without this patch > Exception pointed out by EA Durbin. I in no way am in a position to criticise, but if it turns out not to be applied, you might want to add ok() checks, or at least comments, indicating what you are testing, as it currently doesn't really seem obvious regards, Joris ____________________________________________________________________________________ Don't pick lemons. See all the new 2007 cars at Yahoo! Autos. http://autos.yahoo.com/new_cars.html

1 0

wineprefixcreate - create symlink to cdrom drives(Try 2)
by EA Durbin 03 Apr '07

03 Apr '07

Is there anything wrong with this?

8 11

Re: winspool: Add a test for DeviceCapabilities, fix some bugs found
by Detlef Riekenberg 03 Apr '07

03 Apr '07

On Di, 2007-04-03 at 23:40 +0900, Dmitry Timoshkov wrote: > Changelog: > winspool: Add a test for DeviceCapabilities, fix some bugs found. > + ok(prn_dlg.hDevMode != 0, "PrintDlg returned hDevMode == NULL\n"); > + ok(prn_dlg.hDevNames != 0, "PrintDlg returned hDevNames == NULL\n"); > + > + dm = GlobalLock(prn_dlg.hDevMode); > + ok(dm != NULL, "GlobalLock(prn_dlg.hDevMode) failed\n"); > + trace("dmDeviceName \"%s\"\n", dm->dmDeviceName); > + > + dn = GlobalLock(prn_dlg.hDevNames); > + ok(dn != NULL, "GlobalLock(prn_dlg.hDevNames) failed\n"); > + ok(dn->wDriverOffset, "expected not 0 wDriverOffset\n"); > + ok(dn->wDeviceOffset, "expected not 0 wDeviceOffset\n"); > + ok(dn->wOutputOffset, "expected not 0 wOutputOffset\n"); > + ok(dn->wDefault == DN_DEFAULTPRN, "expected DN_DEFAULTPRN got %x\n", dn->wDefault); > + driver = (const char *)dn + dn->wDriverOffset; > + device = (const char *)dn + dn->wDeviceOffset; > + port = (const char *)dn + dn->wOutputOffset; > + trace("driver \"%s\" device \"%s\" port \"%s\"\n", driver, device, port); > + > + ok(lstrcmp((const char *)dm->dmDeviceName, (const char *)dn + dn->wDeviceOffset) == 0, "device names not match\n"); You are testing "PrintDlgA" in the testsuite for "winspool.drv". The correct location is: dlls/comdlg32/tests/printdlg.c -- By by ... Detlef

1 0

re: Road to 1.0
by Dan Kegel 03 Apr '07

03 Apr '07

Alexandre wrote: > That's still the plan, yes. I'm mostly waiting for the games > support to stabilize; the other main areas, office apps and > installers, both seem in good enough shape at this point. I suppose it depends on your definition of "office apps". Adobe Acrobat Pro and Quicken don't work yet, and they get used in a lot of offices. > I'm also hoping we can make some progress on the x11drv > factorisation before the freeze, so that we don't need to > change the interface too much to add the quartz driver later > on, we'll see how that goes. And if we delay it a bit more > maybe we can slip in Safedisc support too... Oh, yes, please. Here's a try at a 1.0 wish list: - Safedisc support - OpenGL child window problem solved for most common cards at least - Adobe CS2/8 era apps installing and working - Dragon Naturally Speaking 9 working (I'm selfish, I need that one :-) - Quicken 2006 installing/working (including online banking that requires 128 bits) - Mono integration working for non-toy apps - At least some of Munich's VB6 and/or databasey apps working (Hans just submitted a bunch of patches to fix most of the install issues in one) - Better application regression test suite (cxtest, yawt) October is looking about right for the start of the freeze, given that huge list. And my 1.1 wish list (i.e. hard things we can let slip past 1.0): - Activation context support - Quicken 2007 (which requires activation context support?) ... - Dan -- Wine for Windows ISVs: http://kegel.com/wine/isv

10 11

More Direct3D settings in winecfg (was: Enabling GLSL in winecfg)
by Vit Hrachovy 03 Apr '07

03 Apr '07

Hi, according to Stefan, Direct X options regarding * Available Video Memory * Enable GLSL will be useful in winecfg / Graphics section. However there is still missing consensus to how and whether to implement user accessible way to enable/disable GLSL in winecfg. Ray Jones, Stefan and me would like this in winecfg. Please share Your opinion. According to the discussion results, I'm going to add either only Available Video Memory text input box, or both Memory and GLSL toggle checkbox to winecfg. Summary of previous discussion follows: Available Video Memory (text input box) ---------------------- User will input here the RAM size of his graphic card. According to Stefan: "There are vendor dependent ways to read it, but implementing them is pretty nasty(requires some private to winex11.drv). Altough we had that discussion a number of times already and we only agreed on a registry key so far." Enable GLSL (checkbox) ----------- GLSL should be made default in 1.0. However, according to Stefan: "some drivers(*cough* macos *cough*) have serious problems with glsl". Until there is a specification in 1.0 requirements that these issues have to be resolved prior 1.0, this checkbox would be useful even past 1.0. Stefan Dosinger with H. Verbeet pointed out that this option should be in Vertex Shader dropdown box, but after inspecting code, I've found wouldn't blend well with the rest of Vertex Shader idea. This is due to GLSL registry key differs from Vertex Shader registry key. Should they be merged into one? Ivan Gyurdiev pointed out that GLSL can be both enabled for hardware vertex shader and software vertex shader, so the idea of merging GLSL with Vertex Shader dropdown box would result in two menu options - 'GLSL with HW support' and 'GLSL with SW support'. Another stance is to make GLSL enabled by default in next Wine versions. Offscreen Rendering (dropdown box) ------------------- Default option will be 'fbo', optional is backbuffer. Stefan doesn't consider it worthy adding to winecfg. Regards Vit

3 3

Anyone working on XKB support for Wine (or any other Keyboard language detection enhancements)?
by Shachar Shemesh 03 Apr '07

03 Apr '07

Hi all, The current keyboard detection and setting code is based on the traditional method of setting a keyboard in X11. It misdetects most any language that carries a US keyboard as the first group. While major work on other areas of Wine means that most programs today don't really care about that, it still confuses the $*(!@#&$ out of Word. It also has some pretty serious BiDi editing implications. I'm looking into replacing that with code based on the XKB X11 extension, today supported with any quasi reasonable X server. This should totally eliminate the guesswork done through keyboard change detection in wine today. The main question is this - is anyone today already working on this? Thanks, Shachar

3 2

FWD: Art Assets
by Tony Lambregts 03 Apr '07

03 Apr '07

Mike Matis wrote: > Hello, > > I'm not sure if this is the right venue to go through, but It was the > only contact I could find on WineHQ. My name is Mike Matis, and I'd > like to volunteer my skills as an amateur > artist for the Wine project. Specifically, I'd like to make icons, > logos, or other visual assets. I won't waste space in your inbox with > sample images if you have no need of an artist, but if you, do, I > would be willing to provide some samples, or even create a couple > assets on demand to demonstrate if my abilities are desired. I also > have a bit of skill in web design and general aesthetics (graphic and > print). Just give me some guidelines and I'll put myself at your > disposal. > > Hope I can help! > Mike Matis > > > I am forwarding this on to wine-devel since I do not know how we can use your talents but I am sure that there is a way we can use you. ;^) -- Tony Lambregts

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel April 2007