>>Sorry for my earlier post about not getting further activate/deactivate. Yes, indeed, if I click on some other object in the page, then click on the tab again, I get another deactivate/activate pair, as you indicated.
>>
>>However, I think my suggestion about using Activate/Deactivate to track which page is currently active (about 3 minutes ago) should work.
>
>I just think you can't do much about the .Deactivate - it will happen, and you can't know whether it's with a reason or not. However, you can prevent .activate from doing anything if it's trying to activate the currently active page.
>
>Now maybe... if we put some code in .page.mousedown() event, and set the property from there - and if that one fires before the current page's .deactivate, maybe that would solve this puzzle.

Sigh, it won't work. MouseDown doesn't fire on the tab, only if clicked within the page area.