Re: 我也crash啦

[K.O.ed Sephiroth]

Hi all,

To re-produce this crash, just simply hold up/down arrow key while moving mouse above these click entry hotspots. I have post this issue on Welly @ Dept.water BBS.

If I disable the NSTrackingMouseMoved option for all tracking areas, Welly would not crash any more. However, I need to track MouseMoved event in order to make the cursor reasonable.

Here are several solutions:
1. Disable the mouse move tracking and let the cursor go mad.
2. Reduce the number of creation of KOMouseHotspotHandler objects. This may speed up the refreshing of hot spots and may solve the problem. I'm working on this, but I cannot assure this could fix the crashing problem.
3. Reduce the number of refreshing of tracking areas, but this is not so easy. However I believe that there should be some algorithm to solve this problem. Anyone want to think of it?
4. Roll back to old revision.

Regards,

Junliang

2009/2/1 TANG Yang <tangyang.cn@gmail.com>

log见附件，不知如何重现。

--
TANG Yang
Dept. of Computer Science and Technology
Tsinghua University
Tel: (86-10) 51532207

[K.O.ed Sephiroth]

Hi all,

I have finished rewriting the Mouse Hotspot Handle code. Please update to the latest code in trunk and test it brutely:)

Thanks,

- Junliang

2009/2/2 K.O.ed Sephiroth <tale...@gmail.com>

[lu li (gtCarrera)]

Seems this problem has been solved...

On 2月3日, 下午7时59分, "K.O.ed Sephiroth" <talent...@gmail.com> wrote:
> Hi all,
>
> I have finished rewriting the Mouse Hotspot Handle code. Please update to
> the latest code in trunk and test it brutely:)
>
> Thanks,
>
> - Junliang
>

> 2009/2/2 K.O.ed Sephiroth <talent...@gmail.com>

>
> > Hi all,
>
> > To re-produce this crash, just simply hold up/down arrow key while moving
> > mouse above these click entry hotspots. I have post this issue on Welly @
> > Dept.water BBS.
>
> > If I disable the NSTrackingMouseMoved option for all tracking areas, Welly
> > would not crash any more. However, I need to track MouseMoved event in order
> > to make the cursor reasonable.
>
> > Here are several solutions:
> > 1. Disable the mouse move tracking and let the cursor go mad.
> > 2. Reduce the number of creation of KOMouseHotspotHandler objects. This may
> > speed up the refreshing of hot spots and may solve the problem. I'm working
> > on this, but I cannot assure this could fix the crashing problem.
> > 3. Reduce the number of refreshing of tracking areas, but this is not so
> > easy. However I believe that there should be some algorithm to solve this
> > problem. Anyone want to think of it?
> > 4. Roll back to old revision.
>
> > Regards,
>
> > Junliang
>

> > 2009/2/1 TANG Yang <tangyang...@gmail.com>