Hello vitalie, >> I cannot confirm your problem, but you confirmed my problem :)) So, >> maybe I should write that report... > that would be really nice. > after the release rush we will look at this, as we don't like > non-workaroundable problems no less than you do. > the main point of the upcoming release is the increased tough on > the support side, concerning the bugs that are already fixed (but > not yet released). hence, we HAVE TO do this first, as it tends to be the > most distracting. > hope you understand and don't blame us the worst possible way for these > priorities.
:))) Let's just say, your way of business is not my way of business. If you get an email from a customer, who is angry like hell because of the MAPI bug... what do you do? In the worst case you dont answer. But I meet them personally, face by face, he tells me about emails stuck in the Outbox, how angry his boss was, what would YOU say then? Excuses? The real problem with Ritlabs development strategy is that you implement new stuff instead of fix things first... See memory leak, increased system resources, slow exiting, etc. Those should be top priority, not new looks/themes, etc. IMHO. -- Vili ________________________________________________________ Current beta is 3.73 rc 1 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html IMPORTANT: To register as a Beta tester, use this link first - http://www.ritlabs.com/en/partners/testers/
