December 2005 - Wine-Devel - list.winehq.org

Re: continuosly calling the function from winelib failing - stackoverflow

by Dmitry Timoshkov

Ananth M <mekaananth(a)gmail.com> wrote: > - Stub function is declared in XXXXX_dll.h as > long __stdcall STUB_Add(long, long); > -Stub function is defined in XXXXX_main.c as > long __stdcall STUB_Add(long x, long y) > { > printf ("stub function is called \n"); > return 0; > } > > In one Application , I used > LoadLibrary("XXXXX.dll.so") - to load the dll > GetProcAddress("") - to get the function pointer > and if I call the function continuously in a loop of for 1000 > times, first 2 calls are success 3rd call is crashed How do you define a function pointer? Does it have proper number of arguments/ calling convention? If it looks OK to you but still crashes, perhaps you could create a sample project which shows the problem and post an url for it here? -- Dmitry.

Dec. 26, 2005

Re: [bug 4004] MenuItemInfo vs GetMenuString - Try 2

by Dmitry Timoshkov

"Ann & Jason Edmeades" <us(a)edmeades.me.uk> wrote: > In the case of ownerdraw -> string -> ownerdraw, the calls do indeed work > and keep the saved string. Debugging on windows seems to show the string is > copied and saved as well, which concurs with the rest of the patch. > > The fix (rather than the tests) is still accurate for this as far as I can > tell. > > Attached is new patch, which checks the rc of the SetMenuItemInfo (and > InsertMenuItem) calls... The fact that you need to intorduce the txtWasAllocated flag suggests that something is wrong. Also MF_OWNERDRAW certainly does not qualify as a MF_STRING alias. I'll try to play with your test case and see if I can find a better fix. -- Dmitry.

Dec. 26, 2005

Re: [wined3d] D3DXCreateFont

by Aric Cyr

Louis. Lenders <xerox_xerox2000 <at> yahoo.co.uk> writes: > > I had the same problem. Problem is they crash when > version is set to win2000. The default windows version > used to be win98 up to a few months ago, if you switch > back to win98, the bug you describe is absent. Louis I believe I tried that, but it didn't help. I'll double check it anyways though, just to be sure. Thanks for the tip. Out of curiosity, what would make something like this work in Win98 but not Win2000 (or WinXP)? - Aric

Dec. 26, 2005

Should wordpad run yet? It's crashing for me...

by Dan Kegel

I'm trying to narrow down some riched20 problems so I can file bug reports about them. Thinking that perhaps winme's wordpad would be a good test program for this, I tried it out with wine-0.9.4... only to discover it crashes right after displaying its main window. So I filed http://bugs.winehq.org/show_bug.cgi?id=4160 Is there a better way to test riched20.dll interactively? Thanks, Dan -- Wine for Windows ISVs: http://kegel.com/wine/isv

Dec. 26, 2005

Re: LockWindowUpdate status?

by Dan Kegel

On 12/20/05, Dan Kegel <dank(a)kegel.com> wrote: > The last two ISVs I've talked with both had unpleasant > flashing while updating rich text boxes. Both call LockWindowUpdate, > and one ISV mentioned that he had to do that on Windows to > prevent flashing. ... I dug around a bit more; http://www.winehq.org/hypermail/wine-devel/2004/06/0503.html says LockWindowUpdate can't be implemented for real until the update region handing is moved to the server, which is related to http://bugs.winehq.org/show_bug.cgi?id=94, "Rewrite of window management code" and indeed, if you look at Alexandre's to-do list, you see Fix LockWindowUpdate. listed right there. So- is this something Alexandre hopes to fix for 1.0, or is it for later? - Dan -- Wine for Windows ISVs: http://kegel.com/wine/isv

Dec. 25, 2005

Computer down

by Dustin Navea

Sorry to anyone that was working with me on bugs, any anyone that has written to me in the past few days. I got a bigger hdd, and was xferring data from my windows box onto it, then when I went to put my linux hdd into what was formerly my windows box, it wouldnt boot. Looks to be a bad mobo, so I am stuck with only a win box again temporarily. :-( Tom

Dec. 25, 2005

Re: [Bug 4146] first run usability

by Tom Wickline

On 12/25/05, Joseph Garvin <k04jg02(a)kzoo.edu> wrote: > > Those remarks are confusing to me, because winehq.org provides official > binary packages. What's the correct place to report bugs with them if > not the wine bugzilla? I don't see anything on the download page > suggesting that the package maintainers should be contacted directly > instead. That doesn't make much sense anyway, because it's a 'bug' with > all of the packages. None of them provide menu entries or .exe file > association AFAIK. (Admittedly I have only used the SuSE and > Ubuntu/Debian packages in the last year). You did the right thing by submitting the bugs to the data base, all he's saying is there are already bugs filed on this matter. And it's been discussed here on the development list and the bugs are known to the developers. > > Seeing as I was thinking of submitting some usability bugs that might be > considered to be 'package' bugs myself, I'm interested on what the right > thing to do is. Search the data base to make sure you don't file duplicate bug reports. If you don't find a report then file a new one. Cheers, Tom > > >

Dec. 25, 2005

Re: [Bug 4146] first run usability

by Joseph Garvin

wino(a)piments.com wrote: > >> >> ------- Additional Comments From vitaliy(a)kievinfo.com 2005-25-12 >> 10:13 ------- >> This is all belongs in the manual. There were numerous discussions >> about this on >> wine-devel. Wine is not Windows and we do not do things in windows >> ways. It's ap >> to packagers to create any link on the desktop or menu. >> And Wine should not associate itself with *.exe files - again up to >> packagers. >> >> *** This bug has been marked as a duplicate of 75 *** >> > > > > > Those remarks are confusing to me, because winehq.org provides official binary packages. What's the correct place to report bugs with them if not the wine bugzilla? I don't see anything on the download page suggesting that the package maintainers should be contacted directly instead. That doesn't make much sense anyway, because it's a 'bug' with all of the packages. None of them provide menu entries or .exe file association AFAIK. (Admittedly I have only used the SuSE and Ubuntu/Debian packages in the last year). Seeing as I was thinking of submitting some usability bugs that might be considered to be 'package' bugs myself, I'm interested on what the right thing to do is.

Dec. 25, 2005

Re: [Bug 4146] first run usability

by James Hawkins

On 12/25/05, wino(a)piments.com <wino(a)piments.com> wrote: > Does someone want to reign in this fuck-wit before she pisses of the whole > community? > Please calm the language down. If you can't be mature in a discussion, don't be a part of it at all. > > You say you want feedback, suggestions and bug reports yet this is what > happens to constructive input. > Marking a bug as a duplicate or anything else is not a put down. If that were the case, then hundreds of bug reporters should be offended, but they're not. Vitaliy reasonably gave his reasons for marking the bug a duplicate, and the original reporter, or anyone else, can change the bug if they see fit. Concerning the original bug post, the other replies should satisfy your complaints about the outcome of this bug. -- James Hawkins

Dec. 25, 2005

Re: [Bug 4146] first run usability

by Jonathan Ernst

Le dimanche 25 décembre 2005 à 21:47 +0100, wino(a)piments.com a écrit : > Does someone want to reign in this fuck-wit before she pisses of the whole > community? > > How can this be a dupe of a meta bug ?! The meta is supposed to regroup > all such minor bugs. That's why it was created. I don't want to be part of your argument or to question the validity of the resolution your bug has been given; but the first thing I'd do is create separate bugs for separate problems. You should also give a more descriptive title to your bugs. Examples: 1) "wine should not call wineprefixcreate when called without PROGRAM argument" 2) "wine -? and wine -h should be equivalent to wine --help" 3) "wine --help should tell user to check man wine" 4) "wine --help should link to winehq" 5) "wine installation should create links to winecfg in the windows'manager menu" etc. Then you could create a usability meta bug (but meta bugs tend to be not very useful) and link these bugs with it. This way if some of the bugs/enhancement are refused by the developpers you don't loose the chance to see some of your proposed changes to be implemented. This is the same rational behind the fact that big patches that change a million things are rejected: some of your points/change may be valid, but your bug report/patch is useless because it asks/does things that are not accepted by the developpment team. Last thing in http://bugs.winehq.org/show_bug.cgi?id=4146#c1, I don't know why you said sol.exe is a special case and I don't see why we should not tell user that he can use a valid unix path to run applications with Wine. Please try to overcome your little trouble with Vitaliy and keep up with your efforts into helping Wine being more usable. Happy Christmas everyone.

Dec. 25, 2005