- Wine-Devel - list.winehq.org

Re: Re: So lets say we do it
by chrismorgan＠rcn.com Oct. 31, 2002

Oct. 31, 2002

> > 2. People will look for the typical left-side menu: > > Home > > About > > Status > > Development > > Download > > Screenshots > > > > *BZZT* We don't have any. 5% will drop off here. > > Sorry to say that, but in this mail, *you* were talking *some* crap IMHO > ;-) > > We *do* have screenshots. The About page has some pretty nice screenshot. > OK, it's a minimalist approach, granted, but it does show IE etc. > I'd also like to second the opinion that we should have a dedicated "Screenshot" entry right off of the main page. I do the same stuff that Dimitrie does, go to a project, look at some text briefly and then immediately want to see what the app looks like when it is working. So maybe leave the screenshot link off of the "About" page but also put a link on the main page. Chris

1 0

RPC test code?
by Greg Turner Oct. 31, 2002

Oct. 31, 2002

OK, wine made it's first successful RPC's on my box today (yay!) Now, it's time to do a smidgen of housekeeping, and whip up a test. This is a bit tricky, I have a few open questions, which I will enumerate: 1) It feels like cheating to use the same process as client /and/ server. OTOH, it will be a bit cleaner to do it as such... any thoughts on this? specifically, 1a) Will wedging what is basically a winelib app into my test directory create a problem in the configure/make system? Is there a clean way to make sure I invoke the right winelib .exe.so file (the one in my test directory)? 1b) Are all the process-control API's I will need for this in place? (in particular I should kill off the server in case of a failure... will this be a problem? I guess probably not, or else I'd see a lot more wine's hanging around in my process table.) 1c) If the test fails in the winelib thingy, I have to propagate this back to the test; but relying on RPC for this (aside from being unimplemented ATM) is a catch-22, since error propagation might be broken (hence the need for a test)... I guess I can think of creative solutions to this like putting stupid temp files somewhere. Any better ideas? 1d) Anyone know of a problem with this I haven't thought of yet? 2) Whether I use threads or processes, I need some coordination to happen; I am very concerned about race conditions. I want my tests to run under the most absurd and grueling conditions, with NO race conditions. But I can't wrap my mind around how to avoid them ATM. For example: 2a) Should the rpc.c "real" test be the client or the server? I can imagine races either way. Let's say rpc.c is the client. This isn't so bad at a glance; I invoke the server thread/process, and poll RPC from time to time until it goes active (how I do this is another issue, but I'll think of something). Now I do my magic, and request a shutdown via RPC to the server... but, in two cases there is technically a race: first, while I'm invoking the server, I have to wait for it to start as discussed; second, after I send the Shutdown RPC to the server, I have to actually wait for the process/thread to terminate. In both cases, how long is long enough? What if the tests are running on some absurdly bogged down machine that's simultaneously compiling a matrix of 10,000 different wine's, for example? On the other hand, if I use some really liberal timeout like 30 minutes, then in a failure condition, my test would appear to hang, this isn't so great either. If rpc.c is the server, similar problems exist. 2b-?) uh, I guess I squeezed all of these questions into 2a. 3) MIDL? I still haven't figured out the legal ramifications of using midl-generated code. I'd rather not spend a month working on widl before generating a test... so do I need to code my stubs by hand? Even if I do, they're gonna come out looking more-or-less just like MIDL code... maybe I need to figure out the licensing restrictions on MIDL-generated code myself, but does anyone know offhand, I didn't see any obvious discussion of this on microsoft.com or in the platform sdk. ugh. thanks for taking the time to read this long-winded post. Any responses, assistance, flames, etc. are appreciated. -- gmt "The purpose of government is to rein in the rights of the people" --President Bill Clinton, MTV interview, 1993

4 6

Re: SetWindowHookEx
by steve.lustbader＠philips.com Oct. 31, 2002

Oct. 31, 2002

This patch fixed it. Could you change the fixme message in user/hook.c to something more explicit than "won't work right," or at least include a comment in the code explaining why it won't work right? -Steve steve.lustbader(a)philips.com writes: > It's returning NULL for me, which implies it isn't working. Is there some > sort of trace that I can send you to help you out? Oops you are right, this should fix it: Index: server/hook.c =================================================================== RCS file: /opt/cvs-commit/wine/server/hook.c,v retrieving revision 1.1 diff -u -r1.1 hook.c --- server/hook.c 29 Oct 2002 00:41:42 -0000 1.1 +++ server/hook.c 30 Oct 2002 19:51:20 -0000 @@ -227,7 +227,8 @@ set_error( STATUS_INVALID_PARAMETER ); return; } - if (!(thread = get_thread_from_id( req->tid ))) return; + if (!req->tid) thread = (struct thread *)grab_object( current ); + else if (!(thread = get_thread_from_id( req->tid ))) return; if ((hook = add_hook( thread, req->id - WH_MINHOOK ))) { -- Alexandre Julliard julliard(a)winehq.com

1 0

Adobe SVG viewer mouse tracing
by Mike Hearn Oct. 31, 2002

Oct. 31, 2002

Hi, I have CrossOver beta 1.3 and have got IE6 installed and version 3 of the Adobe SVG viewer. The installer doesn't work, but I got around that problem, the issue I'm interested in solving now is that mouse interaction is messed up, namely that when the plugin receives a mousemove event, it appears to immediately receive another for 0,0 - this is just a theory I've got however. I'm wondering if there's a way to restrict debug logging to code in a particular file? I'm not interested in any mouse messages except those to the COM object in NPSVG3.dll thanks -mike

1 0

winapi_check question...
by Greg Turner Oct. 31, 2002

Oct. 31, 2002

winapi_check tells me: ndr_stubless.c:86: rpcrt4: LONG_PTR WINAPIV NdrClientCall2(PMIDL_STUB_DESC,PFORMAT_STRING,...): argument 1 documentation: \ /* CLIENT_CALL_RETURN */ rpc_epmap.c:56: rpcrt4: RPC_STATUS WINAPI RpcEpRegisterA(RPC_IF_HANDLE,PRPC_BINDING_VECTOR,PUUID_VECTOR,LPSTR): no translation defined: PRPC_BINDING_VECTOR rpc_epmap.c:56: rpcrt4: RPC_STATUS WINAPI RpcEpRegisterA(RPC_IF_HANDLE,PRPC_BINDING_VECTOR,PUUID_VECTOR,LPSTR): no translation defined: PUUID_VECTOR rpc_epmap.c:102: rpcrt4: RPC_STATUS WINAPI RpcEpUnregister(RPC_IF_HANDLE,PRPC_BINDING_VECTOR,PUUID_VECTOR): argument 2 type is forbidden: PRPC_BINDING_VECTOR (unknown) how shall I deal with these? -- gmt "The purpose of government is to rein in the rights of the people" --President Bill Clinton, MTV interview, 1993

1 0

Re: miscemu/wine gets into the way in map_image
by Uwe Bonnes Oct. 31, 2002

Oct. 31, 2002

>>>>> "Alexandre" == Alexandre Julliard <julliard(a)winehq.com> writes: Alexandre> Uwe Bonnes <bon(a)elektron.ikp.physik.tu-darmstadt.de> writes: >> However when unzip has unpacked the 160 MByte file and the Setup >> should start, a crash happens, and the debugger startup stops with >> "Memory exhausted". The same happens when I run in winedbg: Loaded >> debug information from ELF >> '/home/bon/tmp/wine/compile/wine/miscemu/wine' (0x00000000) >> Breakpoint 2 at 0x4000c714 (_end+0xf7fec) Memory exhausted. Alexandre> You probably need reduce the base address a bit to leave more Alexandre> space for malloc(). Try changing the 0x3ff to 0x3f0. Now of Alexandre> course we shouldn't be using malloc, so that hack would be a Alexandre> good way to enforce that <g> Alexandre, could we get this into the wine tree? At least one person stumled across that with the same application I had. Bye -- 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

EMF bug
by doome Oct. 31, 2002

Oct. 31, 2002

Hi! I am not sure if this is a bug, or I did something wrong. My collegaues made a little program what shows the bug. It shows an EMF file, but the text boxes appears bad. Two screenshots and the source are included in the tar.gz. Please somebody examine it, and help me if you can. The source, binaries, and screenshots can be downloaded from ftp://ftp.uhulinux.hu/misc/testprg.tar.gz. It needs to be exctracted to the wine c:\ directory Thanks for your help in advance! If needed I can send you wine debug msgs. -- doome

4 3

richedit
by Michael Stefaniuc Oct. 31, 2002

Oct. 31, 2002

Hello, is somebody working on the richedit dll? I encountered 3 unknown RTF control words and wanted to add them but I got scared by the overzealous use of #define's in rtf.h . My first impuls was exchange that with some enum's, but i thought i better ask here before i do the work in vain. bye michael -- Michael Stefaniuc Tel.: +49-711-96437-199 System Administration Fax.: +49-711-96437-111 Red Hat GmbH Email: mstefani(a)redhat.com Hauptstaetterstr. 58 http://www.redhat.de/ D-70178 Stuttgart

3 3

Is it me or is "winedbg --debugmsg -all" not honored
by Uwe Bonnes Oct. 30, 2002

Oct. 30, 2002

Hallo, did I miss something or is it me or is the registry entry ( as advertised in winedefaults.reg) [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\AeDebug] "Debugger"="winedbg --debugmsg -all %ld %ld" not honored any more ( since some time). The relay log is cluttered with about 150k lines of debugger start relay output :-( Bye -- Uwe Bonnes bon(a)elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------

2 1

Re: rpc_H_PL1
by Alexandre Julliard Oct. 30, 2002

Oct. 30, 2002

Greg Turner <gmturner007(a)ameritech.net> writes: > diff -ur -x CVS -x 'bigdif*' ../wine.test/dlls/rpcrt4/rpc_binding.c ./dlls/rpcrt4/rpc_binding.c > --- ../wine.test/dlls/rpcrt4/rpc_binding.c 2002-10-29 12:59:02.000000000 -0600 > +++ ./dlls/rpcrt4/rpc_binding.c 2002-10-29 13:28:39.000000000 -0600 > @@ -865,14 +865,21 @@ > * Exists in win9x and winNT, but with different number of arguments > * (9x version has 3 arguments, NT has 2). > */ > +#ifdef WINNT > +RPC_STATUS WINAPI I_RpcBindingSetAsync( RPC_BINDING_HANDLE Binding, RPC_BLOCKING_FN BlockingFn) > +#else > RPC_STATUS WINAPI I_RpcBindingSetAsync( RPC_BINDING_HANDLE Binding, RPC_BLOCKING_FN BlockingFn, unsigned long ServerTid ) > +#endif > { This can't work, we are not going to build two versions of Wine with different #ifdefs. We should simply decide which version we support (NT would probably be preferable) and get rid of the #ifdefs in the header. -- Alexandre Julliard julliard(a)winehq.com

2 1