C# Tab Control HitTest

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   I'm trying to detect the TabControlItem clicked on by handling the TabControl.MouseUpEvent and then checking TabControl.HitTest(). It never succeeds because it appears that there needs to be a conversion from the MouseUpEvent x,y units to the one that HitTest() uses.
In the TabManager sample, I added the event handler
private void TabControl_MouseUpEvent(object sender, AxXtremeSuiteControls._DTabControlEvents_MouseUpEvent e)
{
    XtremeSuiteControls.TabControlItem item = TabControl.HitTest(e.x, e.y);
    if (item != null)
    {
     ...
    }
}

HitTest() always return null here. The e.y value from the MouseUpEvent is in the range of 0-16. 
I tried the same code in VB, and it works. But the MouseUpEvent in VB returns y values of 0-300. 
My tests with C++ show the same problem as C#. 

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
pchui Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 09 March 2005 Location: United States Status: Offline Points: 1	Post Options Post Reply Quote pchui Report Post Thanks(0) Quote Reply Topic: C# Tab Control HitTest Posted: 27 October 2005 at 7:19pm
	I'm trying to detect the TabControlItem clicked on by handling the TabControl.MouseUpEvent and then checking TabControl.HitTest(). It never succeeds because it appears that there needs to be a conversion from the MouseUpEvent x,y units to the one that HitTest() uses. In the TabManager sample, I added the event handler private void TabControl_MouseUpEvent(object sender, AxXtremeSuiteControls._DTabControlEvents_MouseUpEvent e) { XtremeSuiteControls.TabControlItem item = TabControl.HitTest(e.x, e.y); if (item != null) { ... } } HitTest() always return null here. The e.y value from the MouseUpEvent is in the range of 0-16. I tried the same code in VB, and it works. But the MouseUpEvent in VB returns y values of 0-300. My tests with C++ show the same problem as C#.