On Sat, 2008-07-19 at 12:18 +0200, Tomeu Vizoso wrote: > 2008/7/18 Benjamin Berg <[EMAIL PROTECTED]>: > > We may need a more complicated scheme to keep track of the activities > > during tabbing. > > Much more complicated? Perhaps we should have a TabbingContext class > to keep track of these things, so we don't add too much complexity to > classes like Shell and ShellModel?
The current code assumes that one can just switch the active Activity right away, but only raise the window on a delay. This does not work. I already had some code in my first series of patches that would keep track of a "tabbing-activity" separately from the "active-activity" (in the HomeModel). This, together with some other changes, will be needed to fix the issue. > How bad is this issue from the user point of view? Tabbing is still better than it was before my patches landed. But I do expect that fixing this will be nice improvement in in tabbing experience. > In my opinion, if we can land one important feature like this on one > milestone, and improve its performance on the next one, that's quite > probably the best we can do with the available resources. If we > optimize too late in the release cycle, we may introduce too many bugs > and greatly affect the stability of the whole product. Of course, destabilising sugar should not be an option. I am planning to look into this at the end of next week. So I hope to have a patch by Friday or Saturday. Benjamin
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
