February 2001 - Wine-Devel - list.winehq.org

Re: Misc / Unicode

by Dmitry Timoshkov

"Francois Gouget" <fgouget(a)free.fr> wrote: > <rant> > I checked the other cases and I have this question. Why does everyone > use 0 instead of '\0', 0 instead of FALSE, and '\0' instead of NULL? MS > even does the reverse and uses NULL in places where '\0' or 0 would have > been more appropriate. Man, if you know what you're doing prove it and > use the appropriate form: either 0, '\0' or NULL. > I know this comes from from someone who just forgot to put a trailing > '\0'. But still. > </rant> IMO it doesn't matter in the most cases, if you do not mix pointer data type (NULL) and others. '\0' == 0, and even better to use 0, because it automatically get casted by the compiler to the appropriate data type.

Feb. 6, 2001

Re: Misc / Unicode

by Jon Griffiths

> I know this comes from from someone who just forgot to put a trailing > '\0'. But still. Sounds like a job for winapi_check ;-) BTW, Is Alexandre away? I haven't seen any cvs commits for a week... Jon -- "Don't wait for the seas to part, or messiahs to come, Dont you sit around and waste this chance ..." -Live tntjpgriff(a)tsnxt.co.uk , jon_p_griffiths(a)yahoo.com

Feb. 6, 2001

RE: Reverse engineering court decision

by Patrik Stridvall

> On Tue, 6 Feb 2001, Patrik Stridvall wrote: > > > > Patrik, > > > > > > You are most likely correct. Eventually the court system > > > will get their > > > head out of their ass and figure this out. > > > > I hope so. > > There's optimism for you - they've had their heads there for > years, why > change now? They're just getting comfortable... What do you mean? Who are getting comfortable? The courts? > > > At the moment it > > > seems to me > > > like its way up in there and they are going "Damn, it's > dark in here". > > > > Well, since the DMCA IMHO is logically inconsistant, that > is not very > > suprising. I interpret Judge Kaplan opinion in the DeCSS as "I don't > > really understand this, but if I blame it on Congress and give the > > plaintiff the victory I will probably look less a fool in > the eyes of > > my peers". > > Perhaps. Some of the Slashdot comments on the matter won't > have helped, > though... With peers I was refering to fellow and especially superior court Judges not just anybody that criticized him. What Judge Kaplan basicly said was this is, judging from the letter of the law, what Congress meant and if if they didn't mean this, they should have put it more clearly and if so it is their fault not mine. Shifting blame is quite popular in all sectors of society. :-) > > > Even my dad could easily see the argument that > > > restricting someone from writing a program is really > really braindead > > > (although he has done coding way back in the day). His > > > response was that > > > eventually the court system will figure it out and it'll be > > > over and done > > > with. Seems to be much the same as your response. > > > > Yes, approximately, but don't forget that in the worst case laws can > > be changed and in the meantime enforcing it will be close to > > impossible. > > Indeed. It'll probably survive for a while, but with more and > more holes > being cut... More holes? It is already has holes big as barn doors. :-) One intresting aspect concerning Wine is the DRM (Digital Rights Management) that Slashdot reported that Microsoft are going to add to Windows. If we implement it is Wine we are not trying to circumvent it quite the opposite we are trying to to make it possible enforce it. ;-) Of course a one line patch making a critical function always return TRUE or something might be able to disable it for people that don't like it. :-)

Feb. 6, 2001

RE: Reverse engineering court decision

by James Sutherland

On Tue, 6 Feb 2001, Patrik Stridvall wrote: > > Patrik, > > > > You are most likely correct. Eventually the court system > > will get their > > head out of their ass and figure this out. > > I hope so. There's optimism for you - they've had their heads there for years, why change now? They're just getting comfortable... > > At the moment it > > seems to me > > like its way up in there and they are going "Damn, it's dark in here". > > Well, since the DMCA IMHO is logically inconsistant, that is not very > suprising. I interpret Judge Kaplan opinion in the DeCSS as "I don't > really understand this, but if I blame it on Congress and give the > plaintiff the victory I will probably look less a fool in the eyes of > my peers". Perhaps. Some of the Slashdot comments on the matter won't have helped, though... > > Personally I am glad there are people that are very > > passionate about these > > issues because someone has to bitch about it and start > > getting normal people > > thinking about it. > > Actually I don't think normal people will understand or care very much > until it directly affects them, like why can't I record this TV > program. Indeed. DeCSS never got much attention over here, but 80% of home DVD players are now region de-crippled. > > Even my dad could easily see the argument that > > restricting someone from writing a program is really really braindead > > (although he has done coding way back in the day). His > > response was that > > eventually the court system will figure it out and it'll be > > over and done > > with. Seems to be much the same as your response. > > Yes, approximately, but don't forget that in the worst case laws can > be changed and in the meantime enforcing it will be close to > impossible. Indeed. It'll probably survive for a while, but with more and more holes being cut... James.

Feb. 6, 2001

RE: Reverse engineering court decision

by Patrik Stridvall

> Patrik, > > You are most likely correct. Eventually the court system > will get their > head out of their ass and figure this out. I hope so. > At the moment it > seems to me > like its way up in there and they are going "Damn, it's dark in here". Well, since the DMCA IMHO is logically inconsistant, that is not very suprising. I interpret Judge Kaplan opinion in the DeCSS as "I don't really understand this, but if I blame it on Congress and give the plaintiff the victory I will probably look less a fool in the eyes of my peers". > Personally I am glad there are people that are very > passionate about these > issues because someone has to bitch about it and start > getting normal people > thinking about it. Actually I don't think normal people will understand or care very much until it directly affects them, like why can't I record this TV program. > Even my dad could easily see the argument that > restricting someone from writing a program is really really braindead > (although he has done coding way back in the day). His > response was that > eventually the court system will figure it out and it'll be > over and done > with. Seems to be much the same as your response. Yes, approximately, but don't forget that in the worst case laws can be changed and in the meantime enforcing it will be close to impossible.

Feb. 6, 2001

Re: Misc / Unicode

by Huw D M Davies

On Mon, Feb 05, 2001 at 08:51:45PM -0800, Francois Gouget wrote: > Index: include/richedit.h > =================================================================== > RCS file: /home/cvs/wine/wine/include/richedit.h,v > retrieving revision 1.4 > diff -u -r1.4 richedit.h > --- include/richedit.h 2001/01/22 19:25:27 1.4 > +++ include/richedit.h 2001/01/29 11:01:27 > @@ -15,7 +15,7 @@ > #define cchTextLimitDefault 0x7fff > > #define RICHEDIT_CLASS20A "RichEdit20A" > -#define RICHEDIT_CLASS20W L"RichEdit20W" > +static const WCHAR RICHEDIT_CLASS20W[] = { 'R','i','c','h','E','d','i','t','2','0','W' }; Doesn't this want a trailing 0 ? Huw. -- Dr. Huw D M Davies | Clarendon Laboratory h.davies1(a)physics.ox.ac.uk | Parks Road Tel: +44 1865 272390 | Oxford OX1 3PU Fax: +44 1865 272400 | UK

Feb. 6, 2001

Re: Reverse engineering court decision

by David Elliott

Patrik Stridvall wrote: [BIG BIG SNIP] > > Personally I don't worry that much. First of all I live in Europe > secondly any kind of regulation of these kind of issues will > IMHO be either logically inconsistant or completely arbitrary. > > Neither of the cases are likely to survive in the long run > for several reason among them. > 1. Constitional/"Human rights" reasons > 2. Legal enforcement is close to impossible > 3. It is unlikely to serve the public good Patrik, You are most likely correct. Eventually the court system will get their head out of their ass and figure this out. At the moment it seems to me like its way up in there and they are going "Damn, it's dark in here". Personally I am glad there are people that are very passionate about these issues because someone has to bitch about it and start getting normal people thinking about it. Even my dad could easily see the argument that restricting someone from writing a program is really really braindead (although he has done coding way back in the day). His response was that eventually the court system will figure it out and it'll be over and done with. Seems to be much the same as your response. -Dave

Feb. 6, 2001

Re: debugger fix

by Eric Pouech

Ulrich Weigand wrote: > > Eric Pouech wrote: > > > anyway, I don't think removing the .rel.stab is a big deal. the > > current debugger code doesn't use the address of a global symbol > > in .stab section, but rather rely on the ELF information... > > (but if we also start by removing the .rel.stab section, the > > compilation scheme becomes more and more ugly) > > So, if you use this version of strip_imports, does the Wine build > run through then? well, except from the fact that C comments are not welcomed in SHELL scripts :-O , the rest went fine (at least from the compilation point of view) debugger seemed to run fine... I could set the bp were I wanted there's still a few points I need to look at (especially if ELF addresses are right, and source file location for <x>.spec.c file) I also asked a few .rel.stab questions to the binutils mailing list... last point, couldn't we use a -s option to xargs ? (but I don't know if it's a nice feature of GNU gcc and if it's portable) A+ -- --------------- Eric Pouech (http://perso.wanadoo.fr/eric.pouech/) "The future will be better tomorrow", Vice President Dan Quayle

Feb. 6, 2001

Re: Re: recording sound?

by Thomas Flynn

On Mon, 5 Feb 2001, Eric Pouech wrote: > >winmm wave recording is supposed to be supported, at least at the > >low-level wave API level. Maybe less so at the MCI level, though, > support at the MCI level should be more or less ok... (at least the > Macadamiam folks did a great effort there) > >and not > >supported at all yet in the DirectSound layer. What kind of API does it > > >use to record these sounds? You don't say what kind of app it is... Yeah, I know I didn't say what kind of app it was...I was really just looking for the status of sound recording support. The app is the "COMM1 Radio Simulator" for VFR flight. It's a tool that allows pilots (like myself) to practice their radio communication skills. It's target audience is either newbie pilots or rusty pilots (like myself) who haven't flown in a few years. Essentially, the program presents the pilot with some ATC scenerios and it records the pilot's responses. Afterwards, the pilot can compare his responses to an "expoert" (a proficient pilot). I would figure that it's not a terribly difficult program to write. In addition, it works on both Mac and Windows (two separate binaries, same data files), so I figured it requires pretty generic functionality and is not tightly bound to MS. Sounded like a good candidate to try out on wine :) Recording is the only thing that doesn't work (unfortunately, it's a pretty necessary port in order for the program to be useful). The rest of the program seems to work flawlessly! Great job! Unfortunately, I've reached a point where I need to go through the entire ATC sequences in order for it to be of any benefit. And that means I need to be able to record sound. After using `strings` on a couple of the data files, it appears as though they are data files for Macromedia's Director 6.0. Looking at Macromedia's website (the faq for Director 8...i guess Director 6 is too old), it appears as though one can create executable binaries for both Windows and Mac that show your presentation. Which is what the Comm1 Radio Simulator appears to be a product of. Unfortunately, that's the limit of my knowledge about the app at this point. I'm not a Windows guy. I'm definately a Unix/Linux person. This is the first Windows app I've ever bought. (I really don't want to have to go out and buy a copy of Windows and mess with installing it, just to run this one app). So I downloaded "Preview 1 of CodeWeavers Wine". > post the output of runnnig with the -debugmsg +wave,+mciwave,+dsound > would help us pinpointing the issue Unfortunately, that doesn't seem to be outputting anything to the console for me :(. Perhaps, I'm doing something wrong...I dunno at this point. I suspect it might be easier for me to download the source and compile a debug version of wine myself and see what info I can get out of the app and what it is it might be doing. I'll play with it a bit more and let you guys know what I find out. thanks, tom -- "Mongooses are famous for their snake-fighting ability, and are almost always victorious because of their speed, agility, and timing and also because of their thick coat."

Feb. 6, 2001

Re: Strange window message / queue behaviour

by Ulrich Weigand

Ove Kaaven wrote: > From something (admittedly tangential/irrelevant to this problem) I > remember Ulrich have been talking about (http://www.winehq.com/News/1999-48.html#2, > last paragraph), there's also the possibility that Windows recognizes that > it's a message known to contain pointers, and so just drops the message, > so that EM_GETSEL is simply never dispatched? Yes. EM_GETSEL is classified as 'pointer message', and the 32-bit PostMessage in Win9x simply drops it. (The 16-bit PostMessage doesn't appear to care, but if a 16-bit message with pointers is about to be *received* by a 32-bit app, the Get/PeekMessage call drops the message ...) You get DebugOutput messages like "PostMessage: ignoring posted message with pointer" or "GetMessage: ignoring retrieved message with pointer" when this happens. Bye, Ulrich -- Dr. Ulrich Weigand weigand(a)informatik.uni-erlangen.de

Feb. 6, 2001