wine-devel October 2004

wine-devel@winehq.org

115 participants
272 discussions

Re: Add list for monitoring Appdb
by Tony Lambregts 22 Oct '04

22 Oct '04

Quoting Chris Morgan I was intending to submitt a patch to allow each user to turn on emails. By default no one would recieve emails. If administrators turn on the switch then they would recieve emails from any app that changed. For application Owners/ Maintainers, they would recieve emails when something changed for thier app. The idea for a mailing list archive is so we have a record of what was changed the same way that we have for bugzilla. Mostly it is a safegaurd for when we open up the DB to individual app Owners/maintainers. > > Maybe there should be an option for an admin to add themselves to both a > global and a app specific list so when things change for an app an email is > sent to all people on the global list and then all people on the app specific > list. This lets people opt-in if they want to get the emails. > > Chris > > > On Thursday 21 October 2004 3:58 pm, Jeremy Newman wrote: > > I'm holding off on this patch until I get more comments on why we should > > or shouldn't create yet another mailing list. > > > > My personal opinion is that we don't need a mailing list for this. The > > change emails can go straight to the app owners themselves, and possibly > > to the appdb admins. I know I wouldn't care seeing update emails for > > apps I don't maintain. Just my opinion. > > > > I will create this list if there is enough interest in it. > > > > On Wed, 2004-10-13 at 10:38 -0700, Tony Lambregts wrote: > > > I am working on a series of changes that will let changes to the appdb > > > be emailed to administrators, application owners and other users. > > > > > > This will be similar to how bugzilla does it. > > > > > > When someone changes an application an email listing the changes gets > > > sent to the following > > > > > > - Appdb administrators. > > > - Application owners. > > > - Aplication monitors. > > > > > > One of the things that I think is a repository the way > > > wine-bugs_at_winehq.org does for bugzilla > > > > > > I need Jeremy to set up the email account and the mailman account. > > > > > > Change log: Add link for monitoring changes to application database > > > > > > files changed: lostwages/templates/en/forums.template > > > > > > > > > Tony Lambregts > > > > > > Index: forums.template > > > =================================================================== > > > RCS file: /home/wine/lostwages/templates/en/forums.template,v > > > retrieving revision 1.16 > > > diff -u -r1.16 forums.template > > > --- forums.template 15 Sep 2004 20:05:31 -0000 1.16 > > > +++ forums.template 13 Oct 2004 15:46:24 -0000 > > > @@ -97,6 +97,13 @@ > > > Bug Tracking Database. > > > > > > <li> > > > + [<a > > > href="http://www.winehq.org/mailman/listinfo/wine-appdb">(Un-)Subscribe</ > > >a>] + [<a href="http://www.winehq.org/hypermail/wine-appdb/">Archive > > > </a>] + <a > > > href="mailto:wine-appdb_at_winehq.org">wine-appdb_at_winehq.org</a> + A > > > low traffic (2/day) read-only list for monitoring submissions to the + > > > Application Database. + > > > + <li> > > > [<a > > > href="http://www.winehq.org/mailman/listinfo/wine-tests-results">(Un-)Sub > > >scribe</a>] [<a > > > href="http://www.winehq.org/hypermail/wine-tests-results/">Archive</a>] > > > <a > > > href="mailto:wine-tests-results_at_winehq.org">wine-tests-results_at_winehq.org > > ></a> > > -- > Tony Lambregts > > -- Tony Lambregts

2 1

Re: d3drs_wrap[0-7] ???
by N. Dahn 21 Oct '04

21 Oct '04

Hopefully this isnt the case, and according to this http://msdn.microsoft.com/archive/default.asp?url=/archive/en-us/dx8_c/dire… i have luck for this time i think. :) Comments? Okay, i think i got one step further: on gamedev.net i found the suggestion to use glTexParameteri(GL_TEXTURE_2D, TEXTURE_WRAP_U/V/W, wrapParm). Besides, could this also be an 3D Texture? I think I worked it out and im going to try it out now, but theres one thing bothering me: as mentioned earlier in d3d there exists the d3dwrapcoord_3 flag which wraps textures through the 4th dimension (that should be time). However, i was unable to find _anything_ going into that direction in opengl so i stubbed it out for now. Does anybody know how to proceed with this? BTW, is there a way to figure out what an undocumented function does? (namely d3drs 172 and 173) Cheers Nikolas

3 3

Winedbg: watchpoints broken?
by Walt Ogburn 21 Oct '04

21 Oct '04

Hi, Winedbg's watchpoints don't seem to work for me: when I try to watch a memory location, winedbg responds that a watchpoint has been set at a different, always constant location (I suspect this is actually in winedbg's memory space). Nothing happens when the location I was trying to watch changes. Here is a cut-and-paste from my winedbg session. I try to watch memory location 0x0041a5ec, but I can set other breakpoints and see that the value has changed without the watchpoint taking effect. ----------------------------------------------------------------------- Wine-dbg>run In 32 bit mode. 0x4049a81f start_process+0xcf [/home/reuben/project/wine/wine/dlls/kernel/../../include/winternl.h:1249] in kernel32: jmp 0x4049a815 start_process+0xc5 [/home/reuben/project/wine/wine/dlls/kernel/process.c:1022] in kernel32 1249 static inline void WINAPI DbgBreakPoint(void) { __asm__ __volatile__("int3"); } 1249 static inline void WINAPI DbgBreakPoint(void) { __asm__ __volatile__("int3"); } Wine-dbg>watch *0x0041a5ec Watchpoint 1 at 0x405ae8c4 Wine-dbg>x 0x0041a5ec 00000000 Wine-dbg>break *0x004130ec Breakpoint 2 at 0x004130ec Wine-dbg>cont fixme:ole:CoRegisterMessageFilter stub Stopped on breakpoint 2 at 0x004130ec Wine-dbg>x 0x0041a5ec 403e9d40 Wine-dbg>cond 2 $ecx==0x10 Wine-dbg>cont Stopped on breakpoint 2 at 0x004130ec Wine-dbg>x 0x0041a5ec 00000000 Wine-dbg>info break Breakpoints: 2: y 0x004130ec (1) stop when ($ecx == 16) Watchpoints: 1: y 0x405ae8c4 on 4 bytes (W) -------------------------------------------------------------------------- The fact that winedbg thinks the watchpoint is 0x405ae8c4 is especially puzzling, but it's entirely possible that the confusion lies with me rather than winedbg. Thanks, Walter

2 5

Re: wine/ programs/winhelp/hlp2sgml.c dlls/winsock ...
by Vincent Béron 21 Oct '04

21 Oct '04

Le mar 19/10/2004 à 19:55, Alexandre Julliard a écrit : [snip] > 1.161 1.162 +2 -2 wine/dlls/winsock/socket.c This change removed LONG to put long instead, which is not the same size on Alpha between Windows and Unix. LONG can be made the same size on both. > 1.32 1.33 +2 -2 wine/dlls/rpcrt4/rpc_server.c Same thing here. Shouldn't we use LONG in both places? Vincent

2 1

Re: winedos: per drive current directory
by Eric Pouech 21 Oct '04

21 Oct '04

Markus Amsler a écrit : > Microsoft's Segmented-Executable Linker Version 5.10 shipped with QBasic > 7.1 needs per drive current directory. > > Changelog > * Implement per drive current directory. IMO, you should keep the part of the note dealing with where to store the list of current drives (as it's not done yet in DOS style) A+

1 0

Graphic problems with wxtide32
by Uwe Bonnes 21 Oct '04

21 Oct '04

Hallo, wxtide (http://www.wxtide32.com/download.html) is an opne source program that shows graphic problems. For example, when started, a left click in the tide window brings up a gray window, where some text should appear. This window is managed by following code: static void open_popup(DWORD mouseXY, char *text) { int mouseX, mouseY, cxscreen, cyscreen, startX, startY, side; PAINTSTRUCT ps; RECT purc = {0,0,0,0}; HFONT oldfont; #define POPUP_BORDER 1 close_popup(); // Open window with dummy position and size to get device context popup = CreateWindow("STATIC", "", WS_POPUP|WS_VISIBLE,//|WS_BORDER, 10,10,250,50, window, NULL, t_hinst, NULL); BeginPaint(popup,&ps); oldfont = SelectFont(ps.hdc,gfont); // Get extents for this text DrawText(ps.hdc, text, strlen(text), &purc, DT_CALCRECT); purc.right += POPUP_BORDER*2; purc.bottom += POPUP_BORDER*2; mouseX = LOWORD(mouseXY); mouseY = HIWORD(mouseXY); cxscreen = GetSystemMetrics(SM_CXSCREEN); // cyscreen = GetSystemMetrics(SM_CYFULLSCREEN); if (side=(cxscreen > (mouseX + winX + purc.right))) startX = mouseX + winX; else startX = mouseX + winX - purc.right; if (0 < (mouseY + winY - purc.bottom)) startY = mouseY + winY - purc.bottom; else startY = mouseY + winY; // Now make window the right size and in the right place MoveWindow(popup,startX,startY,purc.right,purc.bottom,FALSE); // SetTextColor(ps.hdc,fgtext_color); // SetBkColor(ps.hdc,RGB(255,255,255)); FillRect( ps.hdc, &purc, GetStockObject(WHITE_BRUSH)); FrameRect(ps.hdc, &purc, GetStockObject(BLACK_BRUSH)); purc.left += POPUP_BORDER; purc.top += POPUP_BORDER; purc.right -= POPUP_BORDER; purc.bottom -= POPUP_BORDER; DrawText(ps.hdc,text,strlen(text),&purc, DT_WORDBREAK|(side? DT_LEFT : DT_RIGHT)); SelectFont(ps.hdc,oldfont); EndPaint(popup,&ps); } Any idea what wine is doing wron? Thanks -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

1 0

Re: msdn: d3drs_wrap[0-7] ???
by Devils Cry 21 Oct '04

21 Oct '04

> yes, its strange. having a real demo of use should help a lot Okay, i tested what i did with a game but the game doesnt call it directly so i guess its right what you said, its done be the d3dtss_address thing. Ill have a _very_ close look at it as my understanding of c isnt that deep atm... > Hmm, i don't think it match exactly OpenGL WRAP specs > but i haven't understand d3d wrapping specs, and i havent seen any > game using it to test :( Try Chaos Legion, its really fun and it uses the wrap calls ;D BTW, for ommiting redundances, ive currently done the d3drs_lineantialias and the ive stubbed out the d3drs_debugmonitortoken call, i think we dont need it. Regards, Nikolas

1 0

Toolbar control Messages causing WM_PAINT
by Thorsten Kani 21 Oct '04

21 Oct '04

I did a quick check of ToolbarMessages that cause WM_PAINT instantly: TB_CHANGEBITMAP TB_CHECKBUTTON TB_DELETEBUTTON TB_ENABLEBUTTON TB_INDERTERMINATE TB_MARKBUTTON TB_PRESSBUTTON TB_SETBITMAPSIZE TB_SETBUTTONSIZE TB_SETBUTTONWIDTH TB_SETCOLOSCHEME TB_SETIMAGELIST TB_SETINDENT TB_SETINSERTMARK TB_SETMAXTEXTROWS TB_SETSTATE I left some the remaining ToolbarMessages untestet because i did not know how to send them correcty with controlspy. other Messages showing up and caused Paint: WM_UNKNOWN(128) WM_CHILDACTIVATE WM_ERASEBKGND WM_MOUSELEAVE(borders) probably this is not everything you need. (: Tho

1 0

Winecfg resources
by David Kredba 21 Oct '04

21 Oct '04

Hello all. There are disabled other than English resources in the wincfg.rc file. I finished tranlating resources to the Czech language and want to enable it. Why are non English resources commented out ? Thanks, David -- David Kredba <kredba at ibot.cas.cz> GPG: ID 1024D/5B6B02DE Fingerprint: F0B3312596BEDCF91DFB 0699E06AACD75B6B02DE

2 1

Re: [wineD3D] HW Vertex Buffer
by Ann and Jason Edmeades 21 Oct '04

21 Oct '04

Hiya, Re your new patch... -#define IWineD3DDevice_CreateVertexBuffer(p,a,b,c,d,e,f) (p)->lpVtbl->CreateVertexBuffer(p,a,b,c,d,e,f) +#define IWineD3DDevice_SetFVF(p,a) (p)->lpVtbl->SetFVF(p,a) +#define IWineD3DDevice_GetFVF(p,a) (p)->lpVtbl->GetFVF(p,a) +#define IWineD3DDevice_CreateVertexDeclaration(p,a,r) (p)->lpVtbl->CreateVertexDeclaration(p,a,r) +#define IWineD3DDevice_SetVertexDeclaration(p,a) (p)->lpVtbl->SetVertexDeclaration(p,a) +#define IWineD3DDevice_GetVertexDeclaration(p,a) (p)->lpVtbl->GetVertexDeclaration(p,a) +#define IWineD3DDevice_CreateVertexShader(p,a,r) (p)->lpVtbl->CreateVertexShader(p,a,r) +#define IWineD3DDevice_SetVertexShader(p,a) (p)->lpVtbl->SetVertexShader(p,a) +#define IWineD3DDevice_GetVertexShader(p,a) (p)->lpVtbl->GetVertexShader(p,a) +#define IWineD3DDevice_CreatePixelShader(p,a,r) (p)->lpVtbl->CreatePixelShader(p,a,r) +#define IWineD3DDevice_SetPixelShader(p,a) (p)->lpVtbl->SetPixelShader(p,a) +#define IWineD3DDevice_GetPixelShader(p,a) (p)->lpVtbl->GetPixelShader(p,a) +#define IWineD3DDevice_CreateVertexBuffer(p,a,b,c,d,e,f) (p)->lpVtbl->CreateVertexBuffer(p,a,b,c,d,e,f) +#define IWineD3DDevice_BindVertexBuffer(p,a) (p)->lpVtbl->BindVertexBuffer(p,a) +#define IWineD3DDevice_UnbindVertexBuffer(p,a) (p)->lpVtbl->UnbindVertexBuffer(p,a) Some of these are defining functions which dont exist yet in wined3d, which will get confusing. Additionally, the functionality for the wined3d vertex buffer is almost untested, because its just copying code and ensuring it gets driven. The d3d9 -> wined3d support isnt enough to prove your changes actually work, and I would rather we didnt put in untested code during the migration phase. I'm finding it hard to keep track of where I am on the migration from d3d8 -> wined3d, so could I ask that you hold off this patch for a month or so, until I can get enought support into the wined3d library so you can prove the new code works. I could do with the d3d8, d3d9 and wined3d code staying fixed as I try to shuffle it all around. Once I get enough in wined3d to be able to prove parts of it work, and we are using it from both d3d8 and d3d9 then by all means put in this change. I'd also comment that this change is desperately needed as hardware buffer support should speed up the d3d support too. It seems odd to turn away new code, especially when hardly anyone else helps on the d3d side! Jason

2 2

← Newer
1
...
8
9
10
11
12
13
14
...
28
Older →

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