On 11.07.2005 14:47, Jonathan Wilson wrote:
> Not that I am any kind of expert here but would it not make sense to
> implement things the way windows does it? From what I know, windows
> implements it via activation contexts and manifests.
Yes, doing it the exact Windows way would require to imple
Frank Richter wrote:
Frank Richter <[EMAIL PROTECTED]>
Add theming support. When comctl32.dll is attached to a thread, a CBT
hook is set up for the current thread which intercepts all window
creations. There, the class name of the window is checked. In case of a
known class, the window is subcla
Hi,
I've worked the suggestions made wrt into that new patch. In particular,
- subclassing is now properly done with SetWindowSubclass
- uxtheme is delay-loaded
- minor things like a correct "hot" flag and more cleanliness due the
better subclassing.
I've uploaded the patch to:
http://www.minet.un
On Thursday 07 July 2005 3:43 am, Frank Richter wrote:
> On 07.07.2005 02:32, Kevin Koltzau wrote:
> > + /* internal stuff */
> > +#define BUTTON_HOT0x8000
> > +#define BUTTON_INTERNAL (BUTTON_HOT)
> >
> > Under windows, the mouseover state is 0x200
>
> Hm, is there a constan
On 07.07.2005 02:32, Kevin Koltzau wrote:
> + /* internal stuff */
> +#define BUTTON_HOT 0x8000
> +#define BUTTON_INTERNAL (BUTTON_HOT)
>
> Under windows, the mouseover state is 0x200
Hm, is there a constant or so for this? Is the mouseover state also
returned by BM_GETS
On Sunday 03 July 2005 9:16 am, Frank Richter wrote:
> Add initial button theming support. Upon initialization, the "Button"
> class is subclassed. In case theming is activated, the subclass will
> take control of painting and state management; without theming, all
> theming-unrelated messages are
