>Again, you take something as an attack. I'm just being honest. If a >product doesn't act as I expect and gives me as much trouble as you seem >to have with PM, then I move to another product. It's as simple as that. >It doesn't matter if it is only one problem. It doesn't matter if the >trouble is in my head or only me and no one else in the whole world. If >the trouble is such a hindrance to my work and enjoyment, and I can erase >it by using something else, then I do it. That's not an attack on you -- >it's business.
OK, you're honest. This is good. But, you see, the way you describe is not exactly how I do things. This is the way I work, just so you know: ·I pick a package because it seems to have features I need and a GUI feeling that is appealing to me. ·I then try to investigate whether it will work for my purposes. The best way is to just use it for at least some real operations, but maybe not as the sole solution. This time, however, the need of a native email client was long overdue and I had to pick one product. PowerMail seemed like it perhaps could both import Emailer messsages, work natively and give me the missing feature most Emailer users seem to want, which in PM is solved with recent messages. I also had hope of faster searching and folder filters. ·If the package doesn't have the features working the way I want or if they are just skindeep, thus not a real solution, I try and determine if this can be worked around and if not, I may consider choosing another package. However, if there are problems that do seem like bug candidates, I usually try and find a way to make it reproducable in order to let the developers have a chance to fix the problem. Usually, developers take an interest in bug canditates and try and remove them in coming incremental updates. Most developers I deal with are not afraid of engaging in communication with parties that want to give information on a specific problem. In the case of PowerMail I was reviewing both an older version to get a feel for the overall way of doing things and also the current version, to let me see if things was different in the newest available version. This is the step where I am now. And in this process it's natural to turn to the user community to see whether the problems A. are known B. have solutions or workarounds C. If not, see if a collaboration with other users could lead to B above. >I'm sorry you're feeling persecuted, Mykael. A lot of people are putting >a lot of time into trying to make suggestions for you. Of course I appreciate when people try and help! Unfortunately though, possibly due to my occasional inability to leave my disappointment and frustration with CTMs lack of action out of my postings, I felt that I was met at least in a few cases, with an attitude that the problems was due to me and not the software at all. I found this was not very productive, as what I wanted to know was if the problems could be fixed in the version I was using or if they were gone in the current version or at least identified so that CTM could have a chance to fix them for the future. But I understand that my sometimes unfortunate way of expressing things have to some extent influenced the reponses I've got. So please let me apologize for my occasional frustrated tone and I'll instead try and explain better what the issues are and the way I see them. >And we welcome >your thoughts and ideas when others are having trouble, too! Thanks.
