Tips & Tricks in EurekaLog, part 1

Many our customers often ask trivial questions about how to do different things with EurekaLog. Well, we have a bit of documentation (chm-file and online one), which describes some public internals, which you can use to customize default behavior. Apparently, this is “dictionary”-like style documentation. In order to use it, you must study all pieces and then come with some way of putting them together to get the desired behavior. Looks like this is too much work for many people, as they continue to ask trivia questions like “My application runs in unattended environment. How can I disable EurekaLog’s dialog?”.

So, I’ve planned few posts about typical usage cases and how you can implement them. This will be sort of Q&A/FAQ-style articles. There are simple questions and answers on them. Answers usually include changing project options or writing a simple bits of code (usually events handlers). Here goes part one.