On Fri, Mar 29, 2013 at 3:08 PM, Siarzhuk Zharski <zharik@xxxxxx> wrote: > Using _Init call is our common practice and is more error-proof than > multiple raw initializations. You must reduce any possibility of future > errors. The code is usually refactored many times - and you have to think > about those who will work on it after you. Just to not be blamed. And it is > obvious, that some time this _Init routine will be extended by adding more > initialization stuff into it some time in the future. So just simplify the > task for your followers and think forward. Okay, no big deal, I'll introduce an _Init() method next time I'm working on Deskbar.