- Wine-Devel - list.winehq.org

Fwd:[Fwd: [AppDB] Status Report]
by Ivan Leo Puoti Dec. 7, 2004

Dec. 7, 2004

Can someone working on appdb fix this? Ivan. ____________________________________________________________ Libero ADSL: 3 mesi gratis e navighi a 1.2 Mega, senza costi di attivazione. Abbonati subito su http://www.libero.it

1 0

Re: No more winrash?
by Ferenc Wagner Dec. 7, 2004

Dec. 7, 2004

Jakob Eriksson <jakov(a)vmlinux.org> writes: > Do you agree, should we stop using winrash? > > "Dmitry Timoshkov" <dmitry(a)baikal.ru> wrote: > >> "Jakob Eriksson" <jakov(a)vmlinux.org> wrote: >> >>> Well, I tried now marking the service as interactive, >>> but that didn't make any difference. >>> >>> So, what follows, deprecate Winrash? >> >> If it really breaks the tests then definitely yes. I think it does provide much useful information which would be largely lost if we resorted to manual testing. What's more, winetest is not really up to that, as it doesn't ask for a tag but relies on a command line option which people would tend to forget. What I propose: make winetest detect whether it's running on an interactive desktop or not, and include this info in the header just like bRunningUnderWine. Meanwhile add the tag dialog to winetest and separate or mark the different reports on the webpage for easier reference. That would bring us the best of both worlds. Or possibly tweak the sensitive tests (how many are there?) to make clear in the output that they were not run for this reason... That would probably require a new field in the final report (ie. success-failure-todo-skipped or similar). This could also signal WINETEST_INTERACTIVE tests so that they aren't forgotten about... That said, I don't know much of this desktop business, so I'm not sure how to put the detection logic in. The rest should not be hard, I hope I'll find the time for them if we decide to go this way. -- Feri.

4 3

Re: Shell about box
by Dmitry Timoshkov Dec. 7, 2004

Dec. 7, 2004

"Ge van Geldorp" <gvg(a)reactos.com> wrote: > Changelog: > Klemens Friedl <frik85(a)hotmail.com> > - Design Shell About dialog more Windows-like The patch will not apply since it's utf-8 encoded. -- Dmitry.

1 0

Re: Implemented CreateAsyncBindCtx
by Alexandre Julliard Dec. 7, 2004

Dec. 7, 2004

Jacek Caban <jack(a)itma.pwr.wroc.pl> writes: > It's my tiny bug. RegsterObjectParam can fail only with E_OUTOFMEMORY > here, so checking it's return is > really not important, but to be correct at all, hres should be just > returned. No, that's worse than before, now you return an error while still allocating the object. You need to cleanup the allocated context when returning a failure. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: Help with some strange debugging.
by Jon Griffiths Dec. 7, 2004

Dec. 7, 2004

Hi Oliver, >I've also got a little patch for oleaut/varient.c to >allow number-string comparisons. There are a couple of >undocumented assumptions I've made,like what to return >for an empty of if the string isn't a number, and the >only thing I've been able to test with is 1 vb >application as I don't have windows, should I post it >to this list or to patch? If you need to test how the native dll works, please write a unit test case for the comparasons you are interested in (there are a _huge_ number of variant tests already defined in the dlls/oleaut32/tests directory). Run the tests manually from the tests directory as: WINEDLLOVERRIDES="oleaut32=n" wine ./oleaut32test.exe.so <testname> To check out the native versions behaviour (of course you will need a native oleaut32.dll in your fake c:\windows\system dir). for the builtin version run: WINETEST_PLATFORM="wine" WINEDLLOVERRIDES="oleaut32=b" wine ./oleaut32test.exe.so <testname> This will catch any regressions from your patch and ensure that future changes don't break your changes in any way. Cheers, Jon ===== "Don't wait for the seas to part, or messiahs to come; Don't you sit around and waste this chance..." - Live jon_p_griffiths(a)yahoo.com __________________________________ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com

1 0

Re: Providing success stories
by Dan Kegel Dec. 7, 2004

Dec. 7, 2004

Stefan Munz wrote: > In order to push the use of Open Source Software we plan a project with the > "Wirtschaftsförderung Region Stuttgart GmbH" ... to > find software producers who pay us for a wine compatibility test of their > software. ... What's the URL, by the way? Is it http://opensource.region-stuttgart.de/ ? > This project is starting at the moment. I thought a good idea to give > something back to the community is to provide some success stories i.e. for > use on winehq.com. Is this interesting? Yes. I don't see anything on winehq.com like that, but http://www.codeweavers.com/site/products/case_studies seems to be along the lines you're thinking of, maybe? Try just writing up a first draft of a success story on a web page somewhere, and post a link to wine-devel so we can see what you're thinking of. Then I'm sure getting it onto winehq.org will be easy. - Dan -- Trying to get a job as a c++ developer? See http://kegel.com/academy/getting-hired.html

3 3

gdi/metafile tests
by Walt Ogburn Dec. 7, 2004

Dec. 7, 2004

To Dmitry Timoshkov - I have started working on some tests (attached here) for metafile functions in gdi. If these seem reasonable, should I add them to your metafile.c test code, or move yours to enhmetafile.c and start a new metafile.h? Thanks, Walter

2 1

Re: msvcrt: implement _dup (take 2)
by Dmitry Timoshkov Dec. 7, 2004

Dec. 7, 2004

"Juan Lang" <juan_lang(a)yahoo.com> wrote: > + if (DuplicateHandle(GetCurrentProcess(), MSVCRT_fdesc[od].handle, > + GetCurrentProcess(), &handle, 0, > + !(MSVCRT_fdesc[od].wxflag & WX_DONTINHERIT), DUPLICATE_SAME_ACCESS)) > + { > + ret = msvcrt_alloc_fd(handle, MSVCRT_fdesc[od].wxflag); > + if (ret == -1) > + *MSVCRT__errno() = MSVCRT_EMFILE; > + } You need to close duplicated handle in the case of msvcrt_alloc_fd failure. -- Dmitry.

2 1

Re: stub implementation for GetLastInputInfo and SetLayeredWindowAttributes
by Dmitry Timoshkov Dec. 7, 2004

Dec. 7, 2004

"Mike McCormack" <mike(a)codeweavers.com> wrote: > +BOOL WINAPI GetLastInputInfo(PLASTINPUTINFO); ... > diff -u -r1.90 user32.spec > --- dlls/user/user32.spec 19 Oct 2004 21:10:17 -0000 1.90 > +++ dlls/user/user32.spec 6 Dec 2004 18:01:17 -0000 > @@ -263,6 +263,7 @@ > @ stdcall GetKeyboardState(ptr) > @ stdcall GetKeyboardType(long) > @ stdcall GetLastActivePopup(long) > +@ stdcall GetLastInputInfo() Number of parameters in header and spec files mismatch and there is no stub implementation of GetLastInputInfo at all. -- Dmitry.

1 0

Fedora Core 2 VM layout
by Kenneth Porter Dec. 7, 2004

Dec. 7, 2004

There's a thread going on the fedora-devel list about exec-shield, legacy_va_layout, and WINE: <https://www.redhat.com/archives/fedora-devel-list/2004-December/msg00132.ht…> Some WINE experts might want to weigh in over there. Are these still issues with the current WINE release?

2 1