Tip for easier MT code debugging

It seems obvious, but I somehow never thought to do this:
When using the Log Window to debug MT code, I always left "Incoming", "Rules", and "Outgoing" checked. Because of that, I'd spend quite a bit of time scanning the Log Window for places where an output might not be what I expected, or where a rule might set a variable incorrectly.
I just belatedly figured out that, if I leave only "Outgoing" checked,or in other cases, only "Rules", I can much more easily pinpoint problem areas. Once they're located, I can check "Incoming" and "Rules" to get a more complete picture of my code.
But then, most of you are probably saying "Duh" to yourselves
Gabriel

One feature I have used with MidiOx was the ability to exclude certain midi messages from the log. I wish this was possible with MTP also, maybe in future versions. If a CC# displays so much information, it is indeed difficult to sift through it all to find exactly what you are looking for.

Gabriels, thanks for sharing. This is the place where people who need such information are likely to find your post!

Ibanman: yes, we plan to include a filter in the Log Window in future versions.

Thanks,
Florian