On Friday 19 November 2004 06:17 pm, William Poetra Yoga H wrote:
> OK, so I think windows/nonclient.c doesn't need to be changed, we just have to
> load a theme somewhere at wineserver startup.
This is an area that is somewhat in the air currently. There are 2 methods I am
toying with to theme st
--- Kevin Koltzau <[EMAIL PROTECTED]> wrote:
> For colors, you don't need to do anything in most cases. Theme colors
> override the default
> system colors for all applications.
>
OK, so I think windows/nonclient.c doesn't need to be changed, we just have
MSDN, the only
> difference is its calling convention.
For colors, you don't need to do anything in most cases. Theme colors override
the default
system colors for all applications.
GetThemeSysColor and GetSysColor are very similar, in most cases just using
GetSysColor
is
--- Mike Hearn <[EMAIL PROTECTED]> wrote:
> No, theming is a breaking change so Windows only applies it to apps that
> opt-in (very smart move IMHO even if the user experience does suffer
> somewhat).
>
>
> Microsoft appear to have done a copy/paste of code from user32 into a new
> comctl DLL
On Tuesday 16 November 2004 02:20 pm, Mike Hearn wrote:
> No, theming is a breaking change so Windows only applies it to apps that
> opt-in (very smart move IMHO even if the user experience does suffer
> somewhat).
On that note, I have been toying with possible ways to start theming common
contro
On Tuesday 16 November 2004 10:38 am, William Poetra Yoga H wrote:
> So, does the app know that it's being themed? What I mean is, for example an
> app is written for Win 95. In the (unlikely case, so let's change it to Win
> ME)
> event that it is compatible with Win XP, will it be skinned (witho
On Tue, 16 Nov 2004 07:38:23 -0800, William Poetra Yoga H wrote:
> So, does the app know that it's being themed? What I mean is, for example an
> app is written for Win 95. In the (unlikely case, so let's change it to Win
> ME)
> event that it is compatible with Win XP, will it be skinned (without
--- Roderick Colenbrander <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Some time ago I looked into uxtheme a bit and it roughly works like this.
> The dll itself is responsible for loading theme files. After a theme is
> loaded it can for example be used to load a bitmap and draw as for example
> the ba
--- Roderick Colenbrander <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Some time ago I looked into uxtheme a bit and it roughly works like this.
> The dll itself is responsible for loading theme files. After a theme is
> loaded it can for example be used to load a bitmap and draw as for example
> the ba
Hi,
Some time ago I looked into uxtheme a bit and it roughly works like this.
The dll itself is responsible for loading theme files. After a theme is
loaded it can for example be used to load a bitmap and draw as for example
the background of a window or it can change the color of controls.
Uxthe
Well, as I said before, I would take a look at uxtheme. Now that I have seen
it, I think I haven't really understood how it works (even after reading a bit
of MSDN).
How does it work, actually? And how to use it? Can anyone give me a simple
explanation? Please look at me as a newbie (I think MSDN
--- Roderick Colenbrander <[EMAIL PROTECTED]> wrote:
> Hi,
>
> Now that I have thought about it a while longer perhaps it is the right idea
> to already start using uxtheme. If I remember correctly uxtheme is already
> usable the only problem is that we don't use it to actually modify the look
>
> No one has other opinions? I still think it's better to use the WinXP
> (classic) colors as the default, until we finish the uxtheme dll (and add
> other themes), because it simply looks better (for me, but I believe others
> also find the new colors more soft to the eye, and comfortable to look
Hi,
On Fri, Nov 05, 2004 at 08:29:56AM -0800, William Poetra Yoga H wrote:
> No one has other opinions? I still think it's better to use the WinXP (classic)
> colors as the default, until we finish the uxtheme dll (and add other themes),
> because it simply looks better (for me, but I believe othe
Hi,
Now that I have thought about it a while longer perhaps it is the right idea
to already start using uxtheme. If I remember correctly uxtheme is already
usable the only problem is that we don't use it to actually modify the look
of wine widgets. Kevin Koltzau, the original uxtheme author, made
I'm sorry, this was supposed to be sent on 03/11/2004... (the patch was resent
on 11/03, but I sent this to my own address instead of winehq.org) So should I
resend the patch again?
And also, for the core devel folks, what do you think about this default color
change?
Message follows:
No one has
--- 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
--- 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
The last time I submitted a patch to change the default system colors from
win95 to winxp (classic), it wasn't merged. I think this was because I didn't
discuss it here.
So now, should we change the default system colors for WINE, from win95 to
winxp (classic)? I really think it l
20 matches
Mail list logo
