- Wine-Devel - list.winehq.org

resource information
by Ivan Leo Murray-Smith March 29, 2004

March 29, 2004

When adding resource information to a wine file, what version should I use? the version string of winxp, win2k3, make it up? Ivan.

1 0

Re: Re: fix crash in winecfg's x11 dialog due to invalid "Desktop" settings
by Mike Hearn March 29, 2004

March 29, 2004

On Mon, 29 Mar 2004 10:11:56 -0500, chmorgan wrote: > Yes, my bad. I'll send in a fixed patch. I still don't like the way the code > looks with the duplication of the default string to use but I couldn't > think of any way to fix it more elegantly. Ideas? Why not just have static char *desktop_default = "640x480" at the top of the function?

1 0

Source code visualization tools?
by Joel Konkle-Parker March 29, 2004

March 29, 2004

Is there such a thing as a source code visualization tool that makes a "map" of a program's source? Kind of like: main() | | function1() /\ / \ func2() func3() | | func4() I'm basically looking for something that will help me "see" how a program is laid out so that I can start working on it. Thanks in advance. -- Joel Konkle-Parker Webmaster [Ballsome.com] E-mail [jjk3(a)msstate.edu]

3 3

Re: Re: fix crash in winecfg's x11 dialog due to invalid "Desktop" settings
by chmorgan＠charter.net March 29, 2004

March 29, 2004

Yes, my bad. I'll send in a fixed patch. I still don't like the way the code looks with the duplication of the default string to use but I couldn't think of any way to fix it more elegantly. Ideas? Chris > > From: Mike Hearn <mh(a)codeweavers.com> > Date: 2004/03/29 Mon AM 06:07:03 EST > To: wine-patches(a)winehq.com > Subject: Re: fix crash in winecfg's x11 dialog due to invalid "Desktop" settings > > On Sun, 28 Mar 2004 13:31:15 -0500, Chris Morgan wrote: > > + if(!bufindex) /* handle invalid "Desktop" values */ > > + { > > + buf = strdup("640x480"); > > + bufindex = strchr(buf, 'x'); > > + } > > It's not a big deal but there's a memory leak there, you need to free buf > before strduping the default (which ideally should be a const str at the > top of the function so if/when we change the default it's only done in one > place). > > thanks -mike > > > >

1 0

Re: Re:bugzilla doesn't find bug
by brettholcomb＠charter.net March 29, 2004

March 29, 2004

I'll try again. On other bugzilla systems I've used the status doesn't make a difference but maybe they default to different selections so I get all the bugs irregardless of status. Thanks. > > From: tony_lambregts(a)telusplanet.net > Date: 2004/03/29 Mon AM 06:45:51 GMT > To: wine-devel(a)winehq.org > CC: brettholcomb(a)charter.net > Subject: Re:bugzilla doesn't find bug > > Brett I. Holcomb wrote > > > If I tell bugzilla to find bugs with winealsa in the summary it does not > > find any at all. However, there is at least one bug - 2035 - with > > winealsa as the first word even! I think bugzilla's broken! > > Works for me. The problem probably that the default selection has unconfirmed > unselected. The one bug that has winealsa as the first word in the summary is > unconfirmed. When I look for winealsa in the comments for all status types I get > 11 bugs listed. > > -- > > Tony lambregts > >

1 0

Re: controls/scroll.c
by Dmitry Timoshkov March 29, 2004

March 29, 2004

"Ge van Geldorp" <gvg(a)reactos.com> wrote: > Changelog: > Ge van Geldorp <gvg(a)reactos.com> > Remove CS_DBLCKS class style from scrollbar class since the > scrollbar doesn't handle double clicks anyway You can't remove it. Scrollbar in Windows has that style, and some applications which subclass it may depend on it. -- Dmitry.

2 4

Re: design problems with thread init code?
by Paul Davis March 29, 2004

March 29, 2004

mike already fixed a bunch of my misunderstandings on IRC. but now i'm faced with the more challenging task of getting this "mono hack" to support threading properly. so feedback is still welcome :) --p

3 4

Re:bugzilla doesn't find bug
by tony_lambregts＠telusplanet.net March 29, 2004

March 29, 2004

Brett I. Holcomb wrote > If I tell bugzilla to find bugs with winealsa in the summary it does not > find any at all. However, there is at least one bug - 2035 - with > winealsa as the first word even! I think bugzilla's broken! Works for me. The problem probably that the default selection has unconfirmed unselected. The one bug that has winealsa as the first word in the summary is unconfirmed. When I look for winealsa in the comments for all status types I get 11 bugs listed. -- Tony lambregts

1 0

Progress on msvcp60.dll?
by Joel Konkle-Parker March 29, 2004

March 29, 2004

Is there any work at all on msvcp60.dll? I haven't seen much mention of it on the lists, and it's not listed on the dll status page. I've found at least one (and heard of more) that require this dll outright, though. Thoughts? -- Joel Konkle-Parker Webmaster [Ballsome.com] E-mail [jjk3(a)msstate.edu]

2 1

design problems with thread init code?
by Paul Davis March 29, 2004

March 29, 2004

hello. i'm the main author of Ardour and JACK, projects those of you with audio/music leanings may be aware of. i'm in the middle of trying to add "native" windows/x86 VST plugin support to these systems, and i ran into some problems. #winehackers suggested to write this list. we are using a modified version of the Mono hack that allows use of winelib as a shared library. i got things working very well until i tried to use a VST plugin that appears to call RtlCreateUserThread. in tracking down why it wouldn't work, i discovered that server_init_thread() is called from the NT DLL for 2 reasons: 1) to initialize the first thread in a winelib-supported program 2) to initialize all later threads there appear to be some problems caused by this. server_init_thread() makes a rather basic assumption: the thread making the request is the target of the request. this is true for case (1) but not for case(2). in case (2), AFAICT, all (most?) instances of "current" need to be replaced by a struct thread* that points to the newly created (but not yet running) thread that is being initialized. it wouldn't suprise me if i have misunderstood things here, but i was able to fix the first problem i encountered (a complaint that the new thread was already running) by adding a kludgy hack based on my understanding. the next problem emerges because the new thread doesn't get its reply/wait fd's set up (instead, the operation is done on "current"). comments? thanks. --p

1 0