On Sun, 31 Oct 2004 16:29:59 -0800, you wrote:
> Roger wrote:
> > I agree that PDT should say "Pacific Daylight Time" but whoever wrote
> > this section refered to both ..DT and ..ST as "Standard Time" for some
> > good reason.I assumed so I followed convention. It came up in an app
> > I was run
What's the current status on bug 423 (http://bugs.winehq.com/show_bug.cgi?id=423),
"Out-of-process COM support"? There hasn't been anything added to
that bugzilla entry for two years, and presumably there has
been some progress. Perhaps someone in the know could
update that bug report.
Likewise,
"Vitaliy Margolen" <[EMAIL PROTECTED]> wrote:
> @@ -761,6 +761,12 @@
>
> case WM_GETDLGCODE:
>result = DLGC_HASSETSEL | DLGC_WANTCHARS | DLGC_WANTARROWS;
> +
> + if (GetWindowLongW( hwnd, GWL_STYLE ) & ES_MULTILINE)
> + {
> + result |= DLGC_WANTALLKEYS;
EDITSTATE structure already
On Mon, Nov 01, 2004 at 01:43:44AM +0100, Thorsten Kani wrote:
> As i understand it, the old Listview code was assuming that
> LVN_GETDISPINFOW is never used and tried to convince apps with the
> "A" version of the Message..
Why are you saying that. The code treats LVN_GETDISPINFOW special
b
Oh, come on, it was just a few more lines of code. In fact, I was happy
with the code as it standed (that's no surprise, as I wrote it :)).
I think we should just revert to it, and accept changes only with
supporting tests. At the time that Aric submitted the patch, I was
rather unhappy with it, b
Roger wrote:
I agree that PDT should say "Pacific Daylight Time" but whoever wrote
this section refered to both ..DT and ..ST as "Standard Time" for some
good reason.I assumed so I followed convention. It came up in an app
I was running as a fixme since we switched to std time today and is used
by
I agree that PDT should say "Pacific Daylight Time" but whoever wrote
this section refered to both ..DT and ..ST as "Standard Time" for some
good reason.I assumed so I followed convention. It came up in an app
I was running as a fixme since we switched to std time today and is used
by TIME_GetTZAs
Roger Olson wrote:
RCS file: /home/wine/wine/dlls/ntdll/time.c,v
retrieving revision 1.51
diff -u -u -r1.51 time.c
--- dlls/ntdll/time.c 22 Oct 2004 19:54:17 - 1.51
+++ dlls/ntdll/time.c 31 Oct 2004 21:18:46 -
@@ -105,6 +105,9 @@
{"AKDT",
{'A','l','a','s','k','a','n',' ','
Jukka Heinonen wrote:
Yep. If using Linux 2.6 kernel and recent pthread library,
threads share the same pid and they must be signalled using
tkill and not kill.
Yes, you're right. I already wondered why dosvm worked before, it was
because I used a 2.4 kernel.
The only place which knows how to
cor
On Sun, 31 Oct 2004 01:26:21 -0800, Jim White <[EMAIL PROTECTED]> wrote:
> Thank you indeed Dan! If I encounter Mike Hearn yet again with his
> "Darwine is Pointless" arguments I can sed 's/Wine/Darwine/ s/Linux/Mac
> OS X/' in reply to him.
Huh?
I just went back through the archives and couldn'
--- Roderick Colenbrander <[EMAIL PROTECTED]> wrote:
> The colors of your gnome/kde desktop don't map that nicely to windows
> colors. Because of this the end-result won't allways be very nice. In the
> future we might want something like this. The best way to add something like
> this is to fini
On Tue, 22 Jun 2004, Alexandre Julliard wrote:
Gerald Pfeifer <[EMAIL PROTECTED]> writes:
...and in fact, Alexandre, wouldn't it be better to have _some_ apps
broken under Wine on FreeBSD than a completely broken Wine on FreeBSD
for all apps?
Nope. What matters is not so much how many apps run to
--- Stefan Dösinger <[EMAIL PROTECTED]> wrote:
> How about using the color setting from the X11 environment? Wine could read
> it
> on startup and convert it to registry keys.
>
Yes, we could do that, but I don't think it's a good idea. Windows programs are
meant to be run on Windows, and peop
> So now, should we change the default system colors for WINE, from win95 to
> winxp (classic)? I really think it looks a lot better with the new colors,
> as the win95 colors are too dull (MS certainly must have done a lot of
> research into this).
How about using the color setting from the X11 en
On Sun, Oct 31, 2004 at 10:50:33AM +, Robert Shearman wrote:
> Yes, that is correct. It would be a lot better to use a boolean flag
> rather than storing the actual format code so that:
> if (infoPtr->notifyFormat == NFR_UNICODE)
> becomes:
> if (infoPtr->bUnicode)
Maybe a bit simpler yes, bu
Dimitrie O. Paun wrote:
On Wed, Oct 27, 2004 at 09:28:33PM +0100, Robert Shearman wrote:
To summarise: *all* common control notifications should be sent in the
same format (ANSI/Unicode) as their parent (except if overriden by the
CCS_SETUNICODEFORMAT message). It should not be based on the me
Andrew Quigley wrote:
What I would like to be able to deploy would be a system which runs
multiple Win32 compatible desktops and multiple logins on a server,
with the clients accessing the desktops via RDP or ICA protocols. How
many of the pieces required to accomplish that already exist, and w
Holly Bostick wrote:
Dan Kegel wrote:
I've run into people several times who dislike the
fact that I advocate or even work on the Wine project,
...
Dan
Dan, first of all, thanks for writing that dowm.
Thank you indeed Dan! If I encounter Mike Hearn yet again with his
"Darwine is Pointless" argume
18 matches
Mail list logo
