- Wine-Devel - list.winehq.org

Re: scanf '%n' fix.
by Tony Lambregts March 10, 2005

March 10, 2005

C. Scott Ananian wrote: > Changelog: > - Allow scanf to continue parsing format string after a '%n'. > (Previously, 'st' wasn't being set, so we'd stop after %n even if > we weren't done with the format string.) Also set 'suppress' > so that the result value returned after a %n is correct. > - Add tests for scanf to check proper handling of '%s %n%s'. > > This fixes a bug I'm seeing in the Windows version of 'sd', a program > for square dance callers ( http://www.lynette.org/sd/ ). Now why is there no AppDB entry for this program. ;^) -- Tony Lambregts

2 1

Re: Wine in the press
by Brian Vincent March 10, 2005

March 10, 2005

On Thu, 10 Mar 2005 17:58:54 +0000, Mike Hearn <mike(a)navi.cx> wrote: > A bit long, and not everyone will know what WGA is. I'd suggest just > paraphrasing it: > > "Wine is the most popular third party translation technology in use" > -Microsoft No, I wouldn't do that. I don't think it's libel, but IANAL and I don't really know. I can't think of a good way to include the quote anywhere on the main page. Maybe it makes more sense starting off the "About" page? Or, even better, we (and by "we" I mean someone other than me) go through some of the articles printed about Wine in the past year and dig out about 5 - 10 really good quotes. Then we (and by "we" I mean Newman) figures out a way to randomly the select the quotes and display them on the main page. Then just include the Microsoft quote with them. I think that would be neat and it would advertise a lot more. In completely unrelated news, I've been meaning to send out something in the next few days reminding people to book hotel rooms for Wineconf. There is still space available - if they told you otherwise please double check. March 17th is the last date for reserving a room there. Also, I need to sit down and spend some time looking over agenda ideas. If you have any ideas at all, or want to present something cool, let me know. - Brian

3 3

Wine in the press
by Tom Wickline March 10, 2005

March 10, 2005

Title: Ham and Wine go well together Link: http://software.newsforge.com/software/05/03/02/1449240.shtml?tid=130 By: Joe Barr <snip> Everything I read said "this is what you want." But of course it isn't, because I don't run Windows. It was just about this time that the news about Microsoft blocking users running Wine from downloading updates and tools from their site began to spread. All the sudden I wondered -- if Wine is good enough to have Microsoft blocking it, could it run CwGet? </snip> All I have to say is "Thank You Microsoft" for the press :-) Tom

9 12

Sorce for Wine MIDI Mapper ?
by Andrew Neil Ramage March 10, 2005

March 10, 2005

Where would I find the source code for this module ? I want to look at it to see if I can discover why it fails to open when using Noteworthy Composer. -- Andrew [hackcoughsniffle] Internal Virus Database corrupt

2 2

Re: server/protocol.def documentation
by Juan Lang March 10, 2005

March 10, 2005

--- Alexandre Julliard <julliard(a)winehq.org> wrote: > protocol.def itself is the documentation of the protocol, there is no > need for more. It's pretty much self-explaining anyway, and people who > can't figure it out by reading the code have no business messing > around with the server protocol. Consider it as the entrance exam for > server hacking ;-) Okay, fair enough. I think what's missing, though, is a dev guide entry on where this thing is, and (briefly) how to extend it. But since experienced wine hackers seem to figure this out anyway, there may be no need. --Juan __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/

1 0

Re: server/protocol.def documentation
by Juan Lang March 10, 2005

March 10, 2005

Hi James, > ie why we use do...while(0) loops in SERVER_START_REQ This is a fairly common idiom in C macros. See here for an explanation: http://www.everything2.com/index.pl?node_id=1180050 Because it's a common trick, I'm not sure it's worth explaining. Describing at a high level what SERVER_START_REQ and SERVER_END_REQ do for the macro-phobic might be useful though. As far as documenting the server API, again I agree with you: it's a worthwhile task. There's even a todo list item for it assigned to Alexandre.. but I wouldn't hold my breath for him to provide something parseable by newbies. If you're starting to understand it, maybe writing it down would be a good idea. --Juan __________________________________ Do you Yahoo!? Yahoo! Small Business - Try our new resources site! http://smallbusiness.yahoo.com/resources/

2 1

Re: Make running tests on a visible desktop a mandatory requirement
by Paul Vriens March 10, 2005

March 10, 2005

On Tue, 2005-03-08 at 17:03, Dmitry Timoshkov wrote: > Hello, > > it appears that new test for a visible desktop works fine, time to make > running tests on a visible desktop a mandatory requirement. > > Changelog: > Dmitry Timoshkov <dmitry(a)codeweavers.com> > Make running tests on a visible desktop a mandatory requirement. > > --- cvs/hq/wine/programs/winetest/main.c Mon Mar 07 14:49:54 2005 > +++ wine/programs/winetest/main.c Tue Mar 08 15:59:02 2005 > @@ -547,6 +547,11 @@ int WINAPI WinMain (HINSTANCE hInst, HIN > const char *cp, *submit = NULL, *tag = NULL; > int reset_env = 1; > > + if (!running_on_visible_desktop ()) { > + report (R_ERROR, "Tests must be run on a visible desktop"); > + exit (2); > + } > + > /* initialize the revision information first */ > extract_rev_infos(); > Apart from the fact whether winrash should be 'fixed' or not, this patch doesn't seem to do what it is supposed to do. Put in other words the running_on_visible_desktop is not correct (enough). I've downloaded http://www.astro.gla.ac.uk/users/paulm/WRT/CrossBuilt/winetest-200503091000… and ran it (interactively of course) on my win98 and win2000 box. It doesn't start and complains with the error (as in the patch) "Tests must be run on a visible desktop". Paul.

3 2

Test suite, todo_wine and different kernels versions
by Uwe Bonnes March 10, 2005

March 10, 2005

Hallo, with kernel 2.6.11 PeekNamedPipe() works as expected. This makes our test suite report: pipe.c:153: Test succeeded inside todo block: peek3 got 21 bytes available pipe.c:186: Test succeeded inside todo block: peek4 got 21 bytes available fixme:sync:SetNamedPipeHandleState 0x38 0x77a2fddc (nil) (nil) pipe.c:153: Test succeeded inside todo block: peek3 got 21 bytes available pipe.c:186: Test succeeded inside todo block: peek4 got 21 bytes available fixme:sync:SetNamedPipeHandleState 0x38 0x77a2fddc (nil) (nil) While removing todo_wine() for this cases silences the output, anybody running on an older kernel will hit an error. How to proceed in that case. Sould he have something like todo_linux(kernelversion){}? Appended a patch to remove these todo_wines, if this is considers the right solution. Bye -- 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/kernel/tests/pipe.c =================================================================== RCS file: /home/wine/wine/dlls/kernel/tests/pipe.c,v retrieving revision 1.14 diff -u -w -r1.14 pipe.c --- wine/dlls/kernel/tests/pipe.c 13 Dec 2004 21:19:02 -0000 1.14 +++ wine/dlls/kernel/tests/pipe.c 10 Mar 2005 11:20:22 -0000 @@ -149,9 +149,7 @@ } else ok(readden == sizeof(obuf), "peek3 got %ld bytes\n", readden); - todo_wine { ok(avail == sizeof(obuf) + sizeof(obuf2), "peek3 got %ld bytes available\n", avail); - } pbuf = ibuf; ok(memcmp(obuf, pbuf, sizeof(obuf)) == 0, "pipe content 3a check\n"); if (pipemode == PIPE_TYPE_BYTE) { @@ -182,9 +180,7 @@ } else ok(readden == sizeof(obuf), "peek4 got %ld bytes\n", readden); - todo_wine { ok(avail == sizeof(obuf) + sizeof(obuf2), "peek4 got %ld bytes available\n", avail); - } pbuf = ibuf; ok(memcmp(obuf, pbuf, sizeof(obuf)) == 0, "pipe content 4a check\n"); if (pipemode == PIPE_TYPE_BYTE) { @@ -228,9 +224,7 @@ ok(written == sizeof(obuf2), "write file len 3b\n"); ok(PeekNamedPipe(hFile, ibuf, sizeof(ibuf), &readden, &avail, NULL), "Peek5\n"); ok(readden == sizeof(obuf), "peek5 got %ld bytes\n", readden); - todo_wine { ok(avail == sizeof(obuf) + sizeof(obuf2), "peek5 got %ld bytes available\n", avail); - } pbuf = ibuf; ok(memcmp(obuf, pbuf, sizeof(obuf)) == 0, "content 5a check\n"); ok(ReadFile(hFile, ibuf, sizeof(ibuf), &readden, NULL), "ReadFile\n"); @@ -260,9 +254,7 @@ ok(written == sizeof(obuf2), "write file len 6b\n"); ok(PeekNamedPipe(hnp, ibuf, sizeof(ibuf), &readden, &avail, NULL), "Peek6\n"); ok(readden == sizeof(obuf), "peek6 got %ld bytes\n", readden); - todo_wine { ok(avail == sizeof(obuf) + sizeof(obuf2), "peek6b got %ld bytes available\n", avail); - } pbuf = ibuf; ok(memcmp(obuf, pbuf, sizeof(obuf)) == 0, "content 6a check\n"); ok(ReadFile(hnp, ibuf, sizeof(ibuf), &readden, NULL), "ReadFile\n");

2 1

Re: New uninstaller #1/3 (RESEND)
by Alexandre Julliard March 10, 2005

March 10, 2005

Jonathan Ernst <Jonathan(a)ErnstFamily.ch> writes: > +#include "resource.h" > +#include "En.rc" The new resource.h file is missing. > -/* BINRES uninstaller.ico */ > -UNINSTALLER ICON MOVEABLE uninstaller.ico > -/* { > - '00 00 01 00 01 00 20 20 10 00 00 00 00 00 E8 02' > - '00 00 16 00 00 00 28 00 00 00 20 00 00 00 40 00' > - '00 00 01 00 04 00 00 00 00 00 00 02 00 00 00 00' You can't remove the icon data, this is needed for the BINRES stuff. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: New uninstaller #1/3
by Mike McCormack March 10, 2005

March 10, 2005

Jonathan Ernst wrote: > Here is the new uninstaller. > > This is the first patch out of 3 of the new installer. > Thanks to Dmitry Timoshkov for helping me a lot with my first win32 program. > > Changelog: > - use dialog instead of window Hey Jonathan, Your patch is still quite big. You've rewritten every function in uninstaller.c, as far as I can tell. Is there any reason you need to do that to convert to using a dialog? I think you may need to break it up even further to get it applied, but the final decision isn't mine. I'd encourage you to write a patch that only converts the window to a dialog, and get that applied first. When that is done, you can think about unicode conversion. Mike

1 0