The only nuisance, what left is chaging the mouse cursor. IMO, SystemNavigation should avoid changing a mouse cursor by itself. It doing so, when codeholder sends: self systemNavigation allCallsOn: aSelector IMO this is wrong: SystemNavigation is a system-wide service tool, and should not assume that image having any UI or mouse cursor, which can be changed during serving queries to it. An outer layer (like UI element), which queries a SystemNavigation could change a cursor, depending on context, but not SystemNavigation itself. On 9 May 2010 23:08, Igor Stasenko <siguctua@gmail.com> wrote:
On 9 May 2010 22:37, Alain Plantec <alain.plantec@free.fr> wrote:
Issue 2403 <http://code.google.com/p/pharo/issues/detail?id=2403>: Annotation pane is slow because of #sendersCount
Le 09/05/2010 21:29, Schwab,Wilhelm K a écrit :
Added fix to that issue. Â (see a changeset in issue tracker)
With it, an annotation pane could be as slow as it wants to, but it doesn't hurth a user's experience, since all information is fetched in background. So, Pharo now could have an ultra-fast method switching, which no longer depends from slowness of annotation panes or its particular options :)
-- Best regards, Igor Stasenko AKA sig.
-- Best regards, Igor Stasenko AKA sig.