I do not skin (don't have the time for it really), but I help people develop software and skins for various platforms. When I find problem I report them and expect them to be fixed. I don't expect excuses for not being able to fix them. I know some things depend on the OS for the "capability", but undoing certain things to be able to do others (like breaking the CMD skinning) I don't like. You should never have to break something to make something else happen. If you have to subtract to "add-hack" the other features then it's not worth it in my book. That's just what I think. I also help devs develop Blackberry Themes and the guys/gals that do that know me as a stickler for perfection. If the theme is off on a certain screen or whatnot by even a small margin I will point it out and get them to fix it. Some of them think I am too picky, but when the product it done and they compare it to the first release they really see how much better it is visually. It's not about pissing anyone off, but I'm just a person who don't like half-assed things. In my book, if you don't want it to look really good, then don't do it at all. Now, like I said, I hadn't noticed this little Aero glitch until yesterday and now I know it's not WB6, so I can't hold that against them and have put it to bed, but the other small glitches I will continue to bicker about because they keep creeping up and it keeps this product from being "really good".
As for my attitude, well, you'll have to deal with that. Don't take it personally, I like to be arrogant and a smart-ass about things I find displeasing. Sometimes it puts people off, but most of the time and when it matters people get the point behind it and fix the problem that caused this type of remark from me. I'll praise your stuff all day long if it's really good. I'll even politely tell you where the issues I'm finding are, but when you're "too good" to fix it I will turn and get on your case until you think I'm being a dick about it. In the end I want the same thing all you guys want. A perfect product that does what it says it does. Right now I have a piece of software that I paid for and loaded which I'm not running due to issues like hibernate hangups and windows not skinning. I am still waiting on a good theme to load which will actually cause me to have it skin my Vista systems for more then 10 minutes before I unload it. It's a shame, but it appears I'll just have to weather it out until the big boys decide it's a good time to start fixing things.
Let me say this.... WB4.6 was freaking AWESOME!!! I loved it and still run it on an older XP box because it skinned everything I ran without any apperent glitches. Some of you might know it had other issues, but it did everything for me. So what if it didn't have transparency or blur or whatever, it did everything else really well. Step forward to WB5.x and above and well........ Seems to me that in the process of trying to bring "Vista like" skinning capabilities to the XP users they had to kill off some things and I don't think it was a good move. I would have done that to bring those new capabilities to XP when Vista was not available and that's what WB5.x did, but once Vista became available for the public I would have fixed the skinning issues in WB and if I was limited to only supporting Vista for the advanced affect, so be it. Either that, or give the people two versions. One for XP with the cutdowns and Vista like affects for those of you who don't care about completeness and one version for Vista users who did everything Aero does and bonded perfectly with the new OS and it's skinning capabilties. Sure it would have been a little more work, but in the end I think it would have been a much better/complete solution. Unfortunatly I don't make those decisions for SD, but I do think it would have been a better approach. That's my viewpoint anyway.