Forums Feature Suggestions A few suggestions..

I'm sure most of us know about MDX.dll. I think it would be nice to
have the additional controls, such as the treeview, already built in. It would also be nice to be able to edit the color and style of the dialog without having to use a dll.

Also, I personally use MCI.dll a lot for playing videos or multiple sounds at once (Like a background sound with sound effects). It would be nice if there were MCI commands and identifiers built in for sound, and possibly joystick control.

If possible, a more accurate $ticks would be nice for picwin freaks.

Being able to script owner-drawn controls, without having to use tons of picwin commands would be a very nice feature, for me. I like being able to customize the look of my mIRC. If it wasn't required to picwin everything, it would be nice.
Skin support would be a nice option as welll.

As a final note, if the smilies are implimented, it would be best if they were customizeable, and could be disabled. To me, and probably a few others, smilies are extremely annoying, and typically very ugly.

Anyways, just my suggestions. Sorry for rambleing so much, and sorry for any spelling/grammar errors, as well.

-TenchiKo

About MDX: IIRC, Khaled has some of the MDX controls planned for the future versions of mIRC. You will just need to wait and see which ones, and when he will put them in.

About video: Not everyone uses this, so it will probably be best to remain as an external DLL.

I don't know if owner drawn controls are possible. They are fairly hard to do even in real programming languages, and are mostly done in programming languages as graphics implimented into the program.

For emoteicons, see: https://forums.mirc.com/s...p;page=0#112012

As a note, I didn't mean soley for video, but just being able to use mci commands without a DLL.

But you do make a good point.

Also, I wasn't sure if owner drawn controls would be possible, but if it was it would be nice.

As a maker of a replacement DLL for MDX (I'm working on it, it's called DCX) and having good experience with the Win32 API, I can tell you that the first step for dialogs is to get rid of the current controls and put real ones in place (mIRC dialog controls are basically all static controls owner drawn to look like real controls because of the old support for 16 bit code).

Then it could possibly extend the controls to include the larger and more complicated ones like the treeview, listview, etc. The one thing that I suspect of keeping Khaled from doing so is that these controls like the treeview and listview have so many options available that it's overwhelming and probably hard to make decisions on what to add or not. The other things is that some of the controls have features that are not accessible across all the span of Win95-98-ME-2k-XP-2k3 and depend mostly on the version of IE installed on the computer.

Finally, I would add that owner drawing controls to perfection is an art to master in API especially if you want more sofisticated controls to support owner-drawn type of things and binding all those possibilities to mIRC would need good thought.