wine-devel February 2004

wine-devel@winehq.org

132 participants
261 discussions

[Winecfg] - redo applications tab, misc changes
by Chris Morgan 04 Feb '04

04 Feb '04

* programs/winecfg/En.rc, appdefaults.c, properties.c, properties.h, resource.h, winecfg.h, x11drvdlg.c, Es.rc, Pt.rc, Ru.rc, Si.rc Chris Morgan <cmorgan(a)alum.wpi.edu> Rename 'General tab' to 'About', move to the last position. Make applications tab handle global and per-app winver, dosver and winelook settings, mirroring the Libraries tab. Code copied from Robert van Herk's libraries tab. Move global/app specific function and global to the x11drv tab where it is currently used. Add a couple of property helper functions. Set 3D border around treeview controls. Removed invalid resources from languages other than En. Comments, questions, suggestions welcome ;-) Chris

2 1

Re: OLEPictureImpl_Load: fix for headerless pictures
by Fabian Cenedese 04 Feb '04

04 Feb '04

>> >> This fails on on my computer and I don't >> >> know how wine could detect if it's a headerless picture or no picture at all >> >> if they look the same (so far). >> > >> >Maybe check header[0] to be real .bmp or .gif magic and header[1] for >> >zero? >> >> I couldn't see a difference, always 0x746c in the first entry. > >Then what type of picture it is? > >0x4947 GIF >0xd8ff JPEG >0x4d42 BMP >0x0000 ICON >0x746c ??? Well, as I didn't use any pictures I don't know what it's supposed to be. Might as well be "NoPic" :) But I have also seen this marker where the second field was not zero. >Have you seen something like "Unknown magic, blah-blah-blah..."? It depends. Without your patch (where [0]=746c, and [1]=0) : trace:ole:OLEPictureImpl_Load (0x40383880,0x414de29c) fixme:ole:OLEPictureImpl_Load icon.idReserved=0 fixme:ole:OLEPictureImpl_Load icon.idType=0 fixme:ole:OLEPictureImpl_Load icon.idCount=0 fixme:ole:OLEPictureImpl_Load [0] width 0 fixme:ole:OLEPictureImpl_Load [0] height 0 fixme:ole:OLEPictureImpl_Load [0] bColorCount 0 fixme:ole:OLEPictureImpl_Load [0] bReserved 0 fixme:ole:OLEPictureImpl_Load [0] xHotspot 0 fixme:ole:OLEPictureImpl_Load [0] yHotspot 0 fixme:ole:OLEPictureImpl_Load [0] dwDIBSize 0 fixme:ole:OLEPictureImpl_Load [0] dwDIBOffset 0 fixme:ole:OLEPictureImpl_Load CreateIcon failed. (obviously when all data are 0) trace:ole:OLEPictureImpl_Release (0x40383880)->(ref=2) trace:ole:OLEPictureImpl_Release (0x40382ec8)->(ref=1) trace:ole:OLEPictureImpl_Destroy (0x40382ec8) trace:ole:OLEPictureImpl_Release (0x40383880)->(ref=1) trace:ole:OLEPictureImpl_Destroy (0x40383880) fixme:ole:OLEPictureImpl_Destroy Unsupported type 0 - unable to delete trace:ole:OLEPictureImpl_Release (0x40380a70)->(ref=1) trace:ole:OLEPictureImpl_Destroy (0x40380a70) trace:ole:OLEFontImpl_ReleaseHfont (0x4037f648)->(0xd82) (lock=0) trace:ole:OLEPictureImpl_Release (0x4037f7a8)->(ref=1) trace:ole:OLEPictureImpl_Destroy (0x4037f7a8) With your patch (already earlier with [0]=756c, [1]=...): fixme:ole:OLEPictureImpl_Load Could only read 109 of 2763 bytes in no-header case? fixme:ole:OLEPictureImpl_Load Unknown magic 746c, 109 read bytes: 6c 74 00 00 00 00 00 00 6c 74 00 00 00 00 00 00 00 00 01 00 00 00 0a 00 54 00 61 00 62 00 20 00 31 00 01 00 00 00 04 52 e3 0b 91 8f ce 11 9d e3 00 aa 00 4b b8 51 6c 74 00 00 00 00 00 00 00 00 00 00 00 00 0a 00 54 00 61 00 62 00 20 00 32 00 01 00 00 00 04 52 e3 0b 91 8f ce 11 9d e3 00 aa 00 4b b8 51 6c 74 00 00 00 00 00 00 00 00 00 00 00 00 ff 02 04 Maybe this isn't even part of a picture and we shouldn't be reading this. How does it know that a picture is coming? Perhaps we shouldn't even enter OLEPictureImpl_Load if there is no picture at all. Thanks bye Fabi

2 1

Orkut community for wine
by Shachar Shemesh 04 Feb '04

04 Feb '04

Hi all, Just so noone else create another community, I have created an Orkut community for Wine. It's located at http://www.orkut.com/Community.aspx?cmm=8767. Sorry about the noise. Shachar -- Shachar Shemesh Lingnu Open Systems Consulting http://www.lingnu.com/

1 0

Mouse up vs Mouse click
by Fabian Cenedese 04 Feb '04

04 Feb '04

Hi Where is decided if I release the mouse button if a mouse up or a mouse click is generated? Is this time dependent? Or generally the same? The misbehaving app uses a ownerdrawn, CListCtrl-derived list. When I click on a cell not in the first column the cell gets selected. But on wine I can see that the selection flashes shortly and disappears right again (Surprisingly it works when I click in the first column. As my application uses the same code for all columns it must be something else.). After putting some debug messages in my code I found that on Windows after the left-button-down event a left-button-click event is generated, no matter how long I hold the button before releasing. On wine there is no click event but a mouse up event. And the cell flashes even when I hold the button, so it's not the releasing itself that clears the selection. The control is a bit quirky with moving focus around and handling events specially. But still it works on Windows :) Now I'm a bit lost how I can debug this. +mouse didn't show anything usefull. I guess the generating and sending of the events is done in the wineserver. Thankful for any hints. bye Fabi

6 22

PPDEV: Allow to switch direction of the printer port
by Uwe Bonnes 04 Feb '04

04 Feb '04

Changelog: dlls/winedos/ppdev.c:IO_pp_outp Allow to switch direction of the printer port This lets mitoujtag.exe access the Jtag chain via the parallel port and a Xilinx parallel cable. -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ---------- Index: wine/dlls/winedos/ppdev.c =================================================================== RCS file: /home/wine/wine/dlls/winedos/ppdev.c,v retrieving revision 1.1 diff -u -w -r1.1 ppdev.c --- wine/dlls/winedos/ppdev.c 17 Sep 2003 22:45:46 -0000 1.1 +++ wine/dlls/winedos/ppdev.c 4 Feb 2004 15:27:00 -0000 @@ -300,7 +300,16 @@ case 0: return IO_pp_do_access(idx,PPWDATA,res); case 2: - return IO_pp_do_access(idx,PPWCONTROL,res); + { + /* We can't switch port direction via PPWCONTROL, + so do it via PPDATADIR + */ + DWORD mode = *res & 0x20; + IO_pp_do_access(idx,PPDATADIR,&mode); + mode = (*res & ~0x20); + return IO_pp_do_access(idx,PPWCONTROL,&mode); + } + case 1: case 0x400: case 0x402:

1 0

Unable to compile under FreeBSD 4.8
by CyberBotX 04 Feb '04

04 Feb '04

I've been trying to compile the latest version of WINE (1-21-2004) under FreeBSD 4.8-RELEASE, but it keeps failing on me with the following during the compile of glu32: gcc -shared -Wl,-Bsymbolic,-z,defs,-init,__wine_spec_init,-fini,__wine_spec_ fini glu32.spec.o glu.o glu32.dll.dbg.o -o glu32.dll.so -L../../dlls -L../../libs/wine -lwine -L/usr/X11R6/lib -lSM -l ICE -lXxf86dga -lXxf86vm -lXrandr -lXrender -lXv -lXext -lX11 -lGL -lGLU -L ../../libs/port -lwine_port -lm -lc /usr/lib/libgcc.a(_eh.o): In function `__empty': _eh.o(.text+0x9e): undefined reference to `pthread_setspecific' /usr/lib/libgcc.a(_eh.o): In function `__get_eh_info': _eh.o(.text+0xec): undefined reference to `pthread_key_create' _eh.o(.text+0x1b9): undefined reference to `pthread_getspecific' _eh.o(.text+0x1d8): undefined reference to `pthread_setspecific' /usr/lib/libgcc.a(frame.o)(.text+0x44b): undefined reference to `pthread_mutex_lock' /usr/lib/libgcc.a(frame.o)(.text+0x492): undefined reference to `pthread_mutex_unlock' /usr/lib/libgcc.a(frame.o): In function `__register_frame_info': frame.o(.text+0x8d9): undefined reference to `pthread_mutex_lock' frame.o(.text+0x900): undefined reference to `pthread_mutex_unlock' /usr/lib/libgcc.a(frame.o): In function `__register_frame_info_table': frame.o(.text+0x969): undefined reference to `pthread_mutex_lock' frame.o(.text+0x990): undefined reference to `pthread_mutex_unlock' /usr/lib/libgcc.a(frame.o): In function `__deregister_frame_info': frame.o(.text+0x9dc): undefined reference to `pthread_mutex_lock' frame.o(.text+0xa27): undefined reference to `pthread_mutex_unlock' frame.o(.text+0xa4d): undefined reference to `pthread_mutex_unlock' *** Error code 1 Stop in /usr/home/cyberbotx/wine/dlls/glu32. *** Error code 1 Stop in /usr/home/cyberbotx/wine/dlls. *** Error code 1 Stop in /usr/home/cyberbotx/wine. I don't know if there is a way to stop it from doing that, but I was told it'd be best to let you guys know. I was trying to compile the source because I've been having problems with the ported version from FreeBSD's site. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.564 / Virus Database: 356 - Release Date: 1/22/2004

1 0

Re: Wineconf wrapup
by Brian Vincent (C) 04 Feb '04

04 Feb '04

> Say, I wanted to thank everyone for coming to Wineconf 2004; > as far as I can tell, a good time was had by all, and we may > even have accomplished one or two useful things <grin>. fyi, I posted a summary in the form of a WWN issue: http://www.winehq.com/?issue=208 If anyone sees any glaring errors or omissions let me know. -brian

1 0

NHL2004 having problems with OLE?; Error output
by Abdul-Haseeb Ahmad 04 Feb '04

04 Feb '04

Okay, so I'm running wine cvs from Feb3 - IE6 installed (installed it on wine20031212 via mike hearn's script and then just used that directory for winecvs) - NHL2004 Demo installed (ftp://ftp.ea.com/pub/easports/demos/nhl2004/NHL2004Demo.exe) & Full version installed - following settings: [AppDefaults\\nhldemo.exe\\Version] "Windows" = "win98" [AppDefaults\\nhldemo.exe\\DllOverrides] "ole32" = "native, builtin" "oleaut32" = "native, builtin" "mshtml" = "native, builtin" "shfolder" = "native, builtin" "shell32" = "native, builtin" "shell" = "native, builtin" "shdocvw" = "native, builtin" "shlwapi" = "native, builtin" "urlmon" = "native, builtin" "crypt32" = "native, builtin" "wininet" = "native, builtin" - ole32, oleaut32 copied from win98 installation, stdole2.tlb from winxp install http://bugs.winehq.org/show_bug.cgi?id=1970 okay, so I can get into the menus with those settings.. ole32/oleaut32 being native reduce the error messages that I get and in the full version lets me navigate around more of the menus.. but I still get some js/html errors.. seems like the HTML files can't read the "global" variables and functions.. im not exactly sure whats going on, i've attached (at http://bugs.winehq.org/show_bug.cgi?id=1970): 1)intro.html which skips the intro videos so you dont get a crash 2)running wine --debugmsg +ole nhldemo (exiting the game as soon as i get into the menus) 3)running winedbg nhldemo, and entering cont a few times until i get into the menu, where i start to get a lot of errors related to the DllUnregisterServer function in the NHL2004 Browser Controls DLL... im hoping someone can help me narrow down the problems here, thanks

1 0

Wineconf wrapup
by Jeremy White 03 Feb '04

03 Feb '04

Hi all, Say, I wanted to thank everyone for coming to Wineconf 2004; as far as I can tell, a good time was had by all, and we may even have accomplished one or two useful things <grin>. I really appreciate that so many of you braved -30C temperature and two days of constant snowfall to come work with us on Wine - such insanity^H^H^H^H^H^H^H^H dedication is admirable. I wanted to suggest that we get to planning Wineconf 2005 sooner rather than later; I'm curious to see which European city hosts the event <grin>. For the record, we're willing to be the major sponsor for the next Wineconf; we'll kick in some funds and person power to help make sure it happens. However, I think it'll only work well in conjunction with one or more locals. I did have some closing thoughts and advice I wanted to get off my chest; there are some things I would do differently next time, and it's probably also wise to touch on the things that worked well. In no particular order, here are a number of thoughts: 1. Screw fancy audio/video streaming. Find an inexpensive telephone conference service, and use it. Test it, several weeks in advance, *with the intended audience* (the stream worked fine on this side of the Atlantic, afaict), and *with the expected load*. Our tests were always done with less load than we had during wineconf, because the streaming traffic used the same pipe as the 'net connection everyone was using. We wasted a lot of time and energy on this, against my initial better judgement, and it proved to be largely useless, afaict from the #wineconf comments. Go low tech. Swallow your geek pride. Just get simple audio that works. /me kicks self 2. Things that worked well: A. An inexpensive location Not one person opted for the expensive hotel I listed; cost really matters to this crowd. The last thing we want to do is scare away young people; they often have enormous energy and no cash. Help with hostels and friends with floors was appreciated. B. Breaks The only times that I was sure that productive conversations were occuring was during the breaks. Provide lots of 'em. Go very light on scheduled topics. C. Do lunch in; that worked really well. Have lots of food and beverages about, that also seems to work well. Bring the water cooler down on the *first* day <grin>. D. Internet connectivity is a must. Really. And provide both wireless and wired. We had some grumpy campers when we initially didn't have enough cat5 ports. E. All of the professional conference paraphenalia was invaluable. A wireless mic (preferably two) and someone to operate it. A PA type system. A projector. Even with the relatively small group we had it was invaluable. 3. Suggestion - blue collar location I know it's fashionable to suggest fancy vacation spots for Wineconf 2005, but I honestly think it would be much better to pick a 'blue collar' venue. Pick somewhere that is a transportation hub, with modest prices. Someplace where some Wine hackers live; having local help is incredibly valuable (thanks to Mandi, Chris, Jon, Aric, Zak, Newman, and all of the gang who did so much work). In fact, when we did go to the fancy tourist night spot, we ended up at a bar where it was too loud to talk; conversation amongst folks from 10 different countries is hard enough without load blaring music or odd ball distractions. A quite room and a good supply of ale, perhaps with a whiteboard, is what folks mostly craved. This is just my $0.02; I think others would differ sharply. 4. The final, critical piece of advice Don't type 'ifconfig eth0 down' in a terminal Window on the Mac in an attempt to reinitialize it's DHCP settings, unless you're dead certain you haven't ssh'd over to the server that is the life blood of your community, and is physically miles away behind locked doors... ...and I still can't figure out why Alexandre won't take my patches! <grin> At any rate, I feel much better now - thanks for listening, and thanks for coming. Cheers, Jeremy

2 1

status of journal hook chain work
by Bill Medland 03 Feb '04

03 Feb '04

I've just tripped over the fact that the journal hook chains are currently not implemented (and were disconnected in October 2002). Does anyone have any plans to do anything about them? -- Bill Medland mailto:billmedland@mercuryspeed.com http://webhome.idirect.com/~kbmed

1 0

Jump to page:

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 February 2004