The dialog is really the only difference between how it works now and your suggestion. A dialog would make tracking logging much easier, but then again, there are many things where dialogs to track the settings could be useful. Where does mIRC stop and let scripting take over? Khaled's been cleaning up settings and simplifying them recently, so adding more to the options may not be something he wants to do.
Other than the issue with two channels that have the same name on different networks, it's pretty easy to set up your own dialog to manage logging. The dialog can simply call /log whenever you open a new window (channel, query, etc) and use either on or off depending on what settings you put into the dialog. That's something that can be set up very easily and in a short amount of time. I doubt you'd have more than 20-30 lines in the script unless you start adding a lot of options to it.
If you want to handle channels on different networks, until mIRC supports different logging settings on a per-window basis that is based on network, you can make this work by using the same dialog method above. Instead of using the built-in logging, you'd just want to create your own logging script. Making your own logging script also shouldn't be that difficuly and it provides you with greater control over how logging works compared to what is available from mIRC.
Either way you do it, it shouldn't take all that long to write and should be all basic commands (nothing requiring expert scripting skills).
All of that said, I'm not against having more logging options or a dialog to manage logging. I just think that it's easy enough to script that it isn't too critical. The one logging thing I *do* want to see improved is the issue with echo causing double timestamps in logs that was mentioned in the bugs forum months ago.
