Shoutbox

quote:

---

Originally posted by CookieRevised
(...)

PSS: From the msdn library:

quote:

---

"When you create a window, the taskbar examines the window’s extended style to see if either the WS_EX_APPWINDOW (0x40000) or WS_EX_TOOLWINDOW (defined as 0x80) style is turned on. If WS_EX_APPWINDOW is turned on, the taskbar shows a button for the window, and if WS_EX_ TOOLWINDOW is turned on, the taskbar does not show a button for the window. A window should never have both of these extended styles. If the window doesn't have either of these styles, the taskbar decides to create a button if the window is unowned and does not create a button if the window is owned."

---

(...)

From the MSDN library:

quote:

---

WS_EX_NOACTIVATE
Windows 2000/XP: A top-level window created with this style does not become the foreground window when the user clicks it. The system does not bring this window to the foreground when the user minimizes or closes the foreground window.

To activate the window, use the SetActiveWindow or SetForegroundWindow function.

The window does not appear on the taskbar by default. To force the window to appear on the taskbar, use the WS_EX_APPWINDOW style.

---

(...)

PS: For the current use in this script:

The showing and hiding of the window isn't needed at all since this function is called before the window is actually shown (as it is now). Setting the new position (as this is often required after a style change since many styles are cached and only read again when you at least set the position of the window (see msdn library again)) or even simply showing the window will be done already by WLM itself.

Also, the "If Then Else" isn't really needed for this script of course, as you will always call the function with the parameter 'false' anyways.

---

quote:

---

Originally posted by CookieRevised
I know about this though, but don't consider it a bug but a known limitation () because as was stated:



It is simply because of WS_EX_NOACTIVATE. If there is a way (event) to know when the user clicks the window, you could call the SetForegroundWindow or SetActiveWindow API....

There is probably a workaround (eg: by simply making a hidden window as the owner of the contactlist, or etc...), but I haven't the time atm to make it. (Ideally you manipulate the taskbar itself and leave the contactlist window totally alone; has probably the advantage that WLM will still be shown in the alt-tab list too)

---