Well, I like mdx very much and its nicely done but i have idea which I have tested before I wrote this post. Its about mIRC Windows and Dialogs. I tried subclassing the windows inside mIRC from my DLL and implementing some new behavior myself but I wasnt able to successifully subclass status or channel window. However, I tried subclassing the mIRC dialog, and I subclassid it with MFC(yea yea I know I know but i am just testing some things.). What I did was create new object and used object.Subclass(mircDialogHwnd). When I did that I gained full control of dialog from my DLL, Any class that MFC has , can be created on that window without host control, behavior of dialog can be altered as well by subclassing windows messages sent to it. So I was just wondering why dont you try to implement something like this? It is far easier to create TreeView control from scratch then subclass existing control and transform it into TreeView or something. Plus If you used MFC or if you converted some cool controls into native Win32 API you could create flat-style looking toolbar, combobox, editbox, stuff like in MS Office.Possibilities are endless because DLL becomes part of mIRC process and can subclass windows inside it. Yes toolbar can be created in dialog window ive tested it out.Only thing that has to be done is make sure that DLL doesnt time out and detach itself from mIRC process, also proper cleanup and restoring of original WndProc needs to be done before dialog is closed. I did some testing on that too just to see what happens.
GPF hehe. Anyway, think about it
its just an idea I had, I would work on it but I dont know if it should be done cuz you already made MDX