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 forwarded to the old button class.
+ /* internal stuff */ +#define BUTTON_HOT 0x80000000 +#define BUTTON_INTERNAL (BUTTON_HOT)
Under windows, the mouseover state is 0x200
+ theme = themingActive ? OpenThemeData( hWnd, themeClass ) : NULL; + set_button_theme( hWnd, theme );
Calling OpenThemeData with a handle associates that theme with the window, which can then be retrieved with GetWindowTheme(hWnd), you don´t need to track the window theme handle yourself
On 07.07.2005 02:32, Kevin Koltzau wrote:
- /* internal stuff */
+#define BUTTON_HOT 0x80000000 +#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_GETSTATE?
Calling OpenThemeData with a handle associates that theme with the window, which can then be retrieved with GetWindowTheme(hWnd), you don´t need to track the window theme handle yourself
Oh, okay.
-f.r.
On Thursday 07 July 2005 3:43 am, Frank Richter wrote:
On 07.07.2005 02:32, Kevin Koltzau wrote:
- /* internal stuff */
+#define BUTTON_HOT 0x80000000 +#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_GETSTATE?
There is no constant, but it is returned in BM_GETSTATE
-
Frank Richter -
Kevin Koltzau