nicklist hwnd - mIRC Discussion Forums

The idea is mainly for my themes. It would be really helpful if you could grab the .hwnd of the nicklist. Perhaps a $window(-4).hwnd.

Or another way to get around my battle with the nicklist menu is make a command to popup menus on command.

Just a thought. Any takers?

Thanks

Have u looked into the Nicklist menu and the identifier $submenu

Code:

menu Nicklist {
  $submenu($heyyou($1))
}
alias heyyou {
  if ($1 == being) { return }
  if ($1 == 1) { return this:echo -a do that }
  if ($1 == 2) { return that:echo -a do this }
  if ($1 == end) { return }
}

What exactly would the hwnd of the nicklist get you? There aren't [m]any mIRC commands that operate on hwnds, so accessing hwnds is pretty much a concern for dlls only. If your question is, "how do I get <insert DLL here> to use my nicklist", that sounds like something you should request with the authors of that DLL.

FWIW, a DLL can get the nicklist's window handle by enumerating the parent channel window, so giving it $window(#).hwnd should be enough information to get what you need.

TY for the reply. I did state the feature request is for theming. Several DLLs could use this hWnd. (or as I said the ability to popup the menu manually)

mIRC is also generous enough to provide you hWnds to the parent and other windows. So that is why I am suggesting that if I have this much information, the amount of depth spent on providing one more hWnd could benefit myself and others.

But the HWND of a nicklist can be easily inferred from the HWND of the parent, which is already available. DLLs already *have* this HWND (or can have it), they're just not exposing it.

I'm not convinced by the argument that because one HWND is available, we should just throw them all in. This leads to bloat in the language. The HWND of the parent window is given because there is no other way to reliably access this value other than querying mIRC for the value, and therefore this is the only way to communicate this information to a DLL. The nicklist, however, can be reliably retrieved by a dll, given the parent HWND, and is NOT needed to be sent over by a script.