April 2004 - Wine-Devel - list.winehq.org

Re: Remove debugmsg from guides
by Dimitrie O. Paun April 26, 2004

April 26, 2004

On Mon, 26 Apr 2004, Ivan Leo Murray-Smith wrote: > attaching as text/plain can't be done for various reasons, so I'll both attach > and inline. Please don't do that, we've been over this a thousand times, let's not rehash it. Do either or, otherwise you end up confusing Alexandre's script, etc. Inlining is prefered for a lot of reasons, so if you're using a decent mail client (and you seem to be), just inline it and don't look back :) -- Dimi.

1 0

Re: RFH: RPC patch
by Ivan Leo Murray-Smith April 26, 2004

April 26, 2004

Running server and client with wine CVS current returns Hello Implicit RPC World! but I can't test with your patch because it doesn't cleanly apply against the current CVS code. Ivan.

1 0

service.cgi: script generation
by Dimitrie O. Paun April 26, 2004

April 26, 2004

Currenly we send a script to run and execute all published versions that we have. This is currently problematic, because an error in one causes the abort the entire script. Moreover, releases may no arrive at the server at the same time, and if we're going to receive the poll event in between them, we'll miss some of them. What we need to do is to ask the client to execute one thing at a time. Problem is that we need to keep track of what the client did execute already. Here's a way to do it without storing state on the server side, which is problematic. We need to introduce three new cookies: build_id: the current build ID that we execute. It's going to be something like '200405031000' current: the name of the test that was just executed history: a comma separated list of filenames that where already executed by the client for this current build. It's going to look like so: 'wine-200405031000-paul-mingw.zip,wine-200405031000-kevin-mingw.zip' The algorithm is simple: if $build_id != $current_build_id $build_id = $current_build_id $history = "" else $history = $history . "," . $current $current = pick_next_test($history) # send script to run $current, and to set the values of the # three cookies to the values in our variables where: pick_next_test picks the next test to run from the pool of tests avaiable for our current build, so that it doesn't appear in $history Comments? -- Dimi.

1 0

Re: Font selection - please review
by Shachar Shemesh April 26, 2004

April 26, 2004

Hi Dirk, First of all, thank you for the reference. Regarding the missing flag to TranslateCharsetInfo - My VisualStudio 6 MSDN DVD (Latest that came up for that version - dated October 2001) does not have this flag mentioned. This means either that the flag was not present at that time, or that it was present but they forgot to mention it (has happened to me before). The latest MSDN (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/intl/unico…) does mention it, and claims it's available on Windows 2000 (like you said). I guess this is anyone's guess what this means as far as when you can use it. Fortunetly for Wine, we don't care when it was introduced. If Wine has it, we can use it. At least for code written by us, that rule is fine. So, thank you very much for the good advice. Are you a wine user that needs this flag, or did you just happen to see my email when you were investigating a Win32 problem? Shachar Dirk Luetjens wrote: > Hello Shachar Shemesh, > > sorry for the lost context. Your mail I replyed to, is available at > > http://www.winehq.com/hypermail/wine-patches/2002/11/0221.html > > I know, that the wine project is totally unrelated to any windows dll. > I thought it would be better to mention, that this additonal flag for > TranslateCharsetInfo is not available in a specific windows version, > since the wine project tries to implement the WIN32 interface, and it > should behave as close as possible to the original one. Judging from > the code in > > http://source.winehq.org/source/objects/font.c#L1849 > > this additional flag is not yet implemented in wine. I can not tell > you when it was introduced into WIN32 itself. The MSDN says something > about WIN2000, but it isn't available on my WIN2k installation. > > Dirk > > > Shachar Shemesh wrote: > >> Hi Dirk, >> >> Judging from the email address you used to send me this email, we are >> talking about a fairly old post. Can you please direct me to the some >> context regarding what was my post exactly? A link with the post in >> question would be very helpful. >> >> Also, I hope you do realize that my post was on a Wine mailing list, >> which means that the functions there are totally disjointed from any >> particular Microsoft version or DLL. >> >> Many thanks, >> Shachar >> >> Dirk Luetjens wrote: >> >>> Hi Shachar Shemesh, >>> >>> I came across your post while researching a problem I had during >>> application development under windows. >>> >>> While digging in the MSDN I found another function that deals with >>> this problem: TranslateCharsetInfo >>> >>> --- >>> TranslateCharsetInfo function translates based on the specified >>> character set, code page, or font signature value, setting all >>> members of the destination structure to appropriate values. >>> --- >>> >>> and for the flag parameter: >>> >>> --- >>> TCI_SRCLOCALE Windows 2000: Source (that is, lpSrc) is the LCID or >>> LANGID of the keyboard layout. If it is a LANGID, the value is in >>> the low word. >>> --- >>> >>> The destination of the translation is a CHARSETINFO structure, where >>> one entry is the charset. >>> >>> I had problems using this parameter, since it isn't implemented in >>> the gdi version I use (VS6, gdi32.dll 5.00.2195.6898). I can only >>> find the definition in the newer .NET studio headers. But perhaps >>> this is a possible inclusion point for your function. >>> >>> Best regards >>> Dirk Luetjens >>> >> >> > > -- Shachar Shemesh Lingnu Open Source Consulting http://www.lingnu.com/

1 0

Re: winmm wave test
by Robert Reif April 26, 2004

April 26, 2004

Francois Gouget wrote: > Some Windows sound drivers allow wild frequencies such as the 2MHz > one. > Is this a windows driver bug? Is the test really valid and it's just finding a real bug in the windows driver for that specific sound card? I know it makes the test fail on bad windows drivers but is that bad?

2 4

email add
by kosta April 26, 2004

April 26, 2004

1 0

Re: Add some functions to msvcrt.dll
by Dmitry Timoshkov April 25, 2004

April 25, 2004

"kata 198" <kata198(a)hotmail.com> wrote: > Changelog: > Add some functions to msvcrt.dll If you could make your patch behave according to current locale that would be really nice. Otherwise it's not acceptable. Also, please make sure that your formatting style is at least consistent, and even better conforms to the formatting style of the file you are editing. -- Dmitry.

1 0

Window management protocol extensions
by Mike Hearn April 25, 2004

April 25, 2004

The latest WM problems caused by Metacity preventing windows from being moved offscreen prompted to raise the issue of having a Wine specific extension to the NETWM (EWMH) protocol into which we can easily add whatever semantics we need to map win32 windowing to X windowing more easily. The idea would be that we have a new property/set of properties we can mark windows with, _NET_WM_WINDOWS_EMULATION for instance, and standards compliant window managers will take note and not do things that break us. Short of actually doing all our own window management, this is probably the best way to fix the obscure bugs caused by different interpretations WMs have of what various hints mean. The current NETWM border hints are semantic not presentational, so we cannot rely on particular intepretations. The MWM hints are even worse - they are apparently undocumented, and most modern WM authors consider them deprecated. Thanks to their undocumentedness, WMs vary in their interpretation of these too: http://bugs.kde.org/show_bug.cgi?id=73294 So, I'd like to start gathering ideas on what sort of things we'd like to have in the NETWM spec, seeing as how many WMs conform to it these days. First up is a way to ensure the WM doesn't attempt to keep the window onscreen of course :) Other things we probably want are related to border styles, an absolutely crystal-clear no-wriggling-possible equivalent to PPosition as apparently the wording of the ICCCM allows WM authors to ignore this if they want. We might also want to look at where we use unmanaged windows and see if we can replace them with the use of managed windows+hints. We can probably hack around the lack of these things for now, but being able to use these hints where possible will probably keep a lot of us from going grey-haired early :) thanks -mike

2 2

RFH: MDI Window menu fix
by Krzysztof Foltman April 25, 2004

April 25, 2004

I've just finished fixing the behaviour of Window menu in MDI applications. However, I'm not sure if it won't cause some other MDI applications to work incorrectly. So, if you have some time and MDI apps to play with (regardless if they worked correctly before or not), check this out and tell me if I've fixed or broken the Window menu. http://www.winehq.org/hypermail/wine-patches/2004/04/0414.html Krzysztof

1 0

Re: abnt2 keyboard patch
by Mauro Carvalho Chehab April 25, 2004

April 25, 2004

Rafael, With your patch, the '\' key on the main keyboard will stop to work on the ABNT2 Keyboard, at least on the ABNT2 keyboards I've tested (some low valued keyboards and also Compaq keyboard). On ABNT2 keyboards, before the 'z' key there is the '\' key and the layout has to reflect that. That was the situation before 200303xx version. That changes was required in order to support that key. Had you tested it? If it works on your keyboard, may be you has some ABNT2 variant. I think it would be better to find another solution for the numeric keyboard that doesn't break the main keyboard. Mauro Chehab > Date: Fri, 16 Apr 2004 10:52:01 -0300 > From: Rafael Ávila de Espíndola <rafael.espindola(a)ic.unicamp.br> > To: wine-devel(a)winehq.org > Subject: Re: abnt2 keyboard patch > > > That's why I said that it's an X11 bug and we can do nothing about it. > > > > Please resubmit the patch without that part. > Attached. I will contact xfree and try to fix the rest of the problem. > > Thanks. > > > Dmitry. > Rafael >

2 1