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

Re: winetest: move to resources (take n+1)
by Alexandre Julliard June 15, 2004

June 15, 2004

Ferenc Wagner <wferi(a)afavant.elte.hu> writes: > Alexandre Julliard <julliard(a)winehq.org> writes: > >> Also I think it would be cleaner to use a different rc >> file for the dist case instead of using #ifdefs. > > I agree. The problem is the single-rc-file limitation, > which would require some code duplication. That's why I > went for the #ifdefs. Please come back at me if you still > have strong feelings about this. What you can do is have a dist.rc file that defines the extra values and then #includes the normal .rc file. This way there is no duplication and no problems with multiple rc files. The only thing is that the code should behave gracefully when the extra resources are missing, but that would be a good thing to do anyway. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: [WineHQ] service.cgi fixes
by Paul Millar June 15, 2004

June 15, 2004

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Dimi, Why remove the verification of the code's gpg signature? It seems to break a basic security maxim: don't trust the network. On Thursday 10 June 2004 22:48, Dimitrie O. Paun wrote: > ChangeLog > Do not include irrelevant stuff in the _history. > Do not instruct the client to verify the .sig, > it's a b0rken idea anyway. - -- Paul Millar -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQFAybhq/9JwS78PA+kRAuv/AJ9Ulntb1MLGn+2gp8r/qpy6VqJDVACePwVB VXxAHr9gaBuMhIJ7P81ahMA= =0tkh -----END PGP SIGNATURE-----

3 5

Latest iteration of the systray patch
by Mike Hearn June 15, 2004

June 15, 2004

This version is resynced against CVS HEAD, and now does a ShowWindow in the right place (just after the embed notification not in some random WM message). This won't be merged so I'm sending it to wine-devel not wine-patches. Getting it merged is blocking on either somebody giving me example code for [un]marshaling an HICON into a block of memory or (best fix) images being moved into the wineserver. This is on Ulrichs todo list but if anybody wants to beat him to it, go ahead, it's still some time off yet. thanks -mike

1 0

Re: Incoming Message
by Twickline June 15, 2004

June 15, 2004

1 0

(no subject)
by Gerald Pfeifer June 15, 2004

June 15, 2004

The following patch to dlls/shell32/shlexec.c revision 1.50 date: 2004/06/15 00:44:14; author: julliard; state: Exp; lines: +11 -3 Dmitry Timoshkov <dmitry(a)codeweavers.com> Restore default "open" functionality of ShellExecute. introduced the following warning regressions: shlexec.c:722: warning: format argument is not a pointer (arg 11) shlexec.c:722: warning: format argument is not a pointer (arg 12) Would you mind fixing this? Gerald -- Gerald Pfeifer (Jerry) gerald(a)pfeifer.com http://www.pfeifer.com/gerald/

1 0

Re: Incoming Message
by Twickline June 15, 2004

June 15, 2004

1 0

Re: Yahoo!
by Johane June 15, 2004

June 15, 2004

1 0

Do we still need wineinstall?
by Mike Hearn June 15, 2004

June 15, 2004

Hi, I've been running without a config file for a while now, and have fixed various misc bugs related to that as I go - I'm sure there are some more in there, but as the config file is destined for eventual doom anyway I am wondering if we still need wineinstall at all? Currently, it's possible to use Wine quite succesfully just by doing a standard ./configure, make, make install. When you run wine for the first time wineprefixcreate will be used to setup ~/.wine, merge the registry, create the fake windows drive and so on. The only piece you don't get is the default config file, but that doesn't seem to make much difference any more. At least, the defaults should be in the code not the config file as people never upgrade that bit anyway :) So - do we still need it?

2 1

Re: winetest: move to resources (take n) (resend)
by Alexandre Julliard June 14, 2004

June 14, 2004

Ferenc Wagner <wferi(a)afavant.elte.hu> writes: > This is a resend to elicit some feedback on your objections > against this patch. What did I miss again? It's much better this time. The only thing I would suggest changing is that the build info text formatting should be done in the code, not in the makefile. Also I think it would be cleaner to use a different rc file for the dist case instead of using #ifdefs. -- Alexandre Julliard julliard(a)winehq.org

1 0

Re: Create DIALOGINFO On Demand When Calling DIALOG_get_info
by Alexandre Julliard June 14, 2004

June 14, 2004

Robert Shearman <R.J.Shearman(a)warwick.ac.uk> writes: > This patch fixes bug 2210: > http://bugs.winehq.org/show_bug.cgi?id=2210 > This patch differs slightly from the one posted to wine-devel, as it > includes some checks for NULL return from DIALOG_get_info. I don't think you want to create the dialog info in all cases, this should only be done where we are sure we have a dialog window. For instance you don't want MapDialogRect to add dialog info to arbitrary windows just because it got passed a wrong handle. -- Alexandre Julliard julliard(a)winehq.org

1 0