And you are starting to illustrate that you just shoot down new features for the heck of it.

Quote:

As much is he will implement, people will always want more control. And the UI's change faster than any one person can keep up with.


We can both go over the list and pick out the truly silly requests that would require too much work at low level for too little gain or which are relatively new to the API. Sso im not talking about those but adding an UpDown, Treeview or an ListViewEx (too name some new features) are all controls that would be used extensively.

As such, i dont see how what Onslaught suggested is any problem at all These are some pretty basic low level events that could be added withouth too much hazzle.

He didnt even mention autocompletion nor does his images show any form of autocompletion just keydown validation and ghost texts which is supported in the win32 api directly already as well and shouldn't be any hassle to add as well, although ghost texts are relatively new they could be scripted using focus events and some more control over the font and colours.

You make all the wrong assumptions here:
  • Khaled himself added dialog support
    So your question "Is mIRC an IRC client, or is it a windowing toolkit?" is completely irrelevant nor any reason to shoot down new features.
  • Khaled himself chose to make a high level script engine
    So shooting down any new features because a low level approach might be better is again irrelevant and no reason to shoot them down. Low level control is even less likely to happen.


The fact remains that there are alot of controls/events/commands that can (and perhaps should) be routed to be controled from mIRC that wouldnt take too much work. For those who want complete control over everything should look into making picwin GUI's or think twice whether mIRCScript is even the right tool for the job.


$maybe