On Wed, Jan 10, 2007 at 02:28:36PM -0500, MenTaLguY wrote:
Has a bug been filed, ideally including the movie as an attachment, so that this issue doesn't get forgotten?
Yes, there is a bug report in on it - the bug id was referenced in the initial post. (Btw, for future reference, when discussing bugs on the mailing list, it would be immensely helpful to preserve the bug ID, either in the subject line or the body.)
Momo, thanks for taking the time to create a movie of what you're seeing; it demonstrates very clearly the effect. I attempted to recreate it but like Bulia was unable to do so on my machine. What would be ideal is if we could find a second person who can reproduce it, and then we can see what is common between their environment and yours - and what is difference between yours and those who can't reproduce it.
I think we should focus on this for 0.45, but if it turns out to be very difficult to replicate and/or fix, probably what will happen is that we release 0.45 as-is, and address this along with any other missed bugs in a follow-up 0.45.1 release. That's often been the way we've had to do things in the past.
While this is certainly an annoying bug to have in this new feature, I don't think it meets the criteria for being a MUST FIX bug. It does not cause crashes or data loss - just annoying usability issues. We also do not yet have a developer who can reproduce it and take ownership of it.
I know it seems bad to release a new feature with some bugs remaining it it, but like mental says, this is not new. New features are rarely perfect right out of the gate, and getting all the polish into them can stretch out a long time. If we waited until they were perfect, we'd have to delay the release far too long, so it's often preferred to release with the features most of the way there. The layers feature is just such an example - the core functionality was created in one release, but it took 2-3 more releases before we had a layer dialog and all the assorted niceties to go with it.
For this release, with the blur feature it is crashes we should be most worried about. I think people will tolerate some quirkiness of a new feature (as long as we iron out the quirks in a subsequent release), but crashes will really sour them to the feature.
Bryce