Always simulate a mouse movement after animations in the Linux tabstrip to ma...

Always simulate a mouse movement after animations in the Linux tabstrip to make sure we never have a stale hover index.

Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=14743

[tony, 2009-04-28 17:27:24]

Rather than simulating a mouse move, can't we call directly into the
OnMotionNotify function?  It's kind of awkward since it takes params that you
don't have, but maybe you could refactor OnMotionNotify to call a new method on
TabStripGtk that only takes the parts of |event| that you need?

[James Hawkins, 2009-04-28 17:34:09]

On 2009/04/28 17:27:24, tony wrote:
> Rather than simulating a mouse move, can't we call directly into the
> OnMotionNotify function?  It's kind of awkward since it takes params that you
> don't have, but maybe you could refactor OnMotionNotify to call a new method
on
> TabStripGtk that only takes the parts of |event| that you need?

I did think about that option, but I'd rather not for a few reasons.
* This is how it's done in Windows.
* Adding a wrapper that we can call too is awkward.
* I forgot to add a TODO that says this will all go away when I make each tab a
widget (which will be happening soon).

So I'd like to keep it this way, with an added TODO and then work on making each
tab a widget, which will move all of this hovering hack disappear.

[tony, 2009-04-28 17:41:16]

Ok, if you promise that this hack won't appear in the refactor.  It makes it
harder to debug if it jumps back and forth between gtk and our code.

On 2009/04/28 17:34:09, James Hawkins wrote:
> On 2009/04/28 17:27:24, tony wrote:
> > Rather than simulating a mouse move, can't we call directly into the
> > OnMotionNotify function?  It's kind of awkward since it takes params that
you
> > don't have, but maybe you could refactor OnMotionNotify to call a new method
> on
> > TabStripGtk that only takes the parts of |event| that you need?
> 
> I did think about that option, but I'd rather not for a few reasons.
> * This is how it's done in Windows.
> * Adding a wrapper that we can call too is awkward.
> * I forgot to add a TODO that says this will all go away when I make each tab
a
> widget (which will be happening soon).
> 
> So I'd like to keep it this way, with an added TODO and then work on making
each
> tab a widget, which will move all of this hovering hack disappear.