I''ve been studing a common samples of Essential Tools (VS.NET Demo) when I saw following issue:
When child frame contains TabControl (i.e. like a StartPage) all keyboard input is somehow intercepted by TabControl. Wherefor if user tries to use keyboard to navigate menu, he fails.
Is there any way to solve this problem? (Essential Studio 220.127.116.11 on .Net 1.1+SP1 )
ADAdministrator Syncfusion Team May 6, 2005 10:15 AM
I loaded the sample on my system and tested for this problem and was unable to reproduce it. Are you using Windows XP? If not, please let me know and I''ll test the sample on a different operating system. Any other relevant information about your system would help as well. Thank you for your cooperation.
NONonExistoMay 10, 2005 01:33 AM
I''m using wXP+SP2(build in) and proplem still apear on my desktop. So let me explain it step by step.
Well I lunch the application and press and resease ALT key (to highlight main menu). Then I use a arrows to navigate menu like this: down, right, right, down, down.. When menu loses input.
I don''t think it''s a TabControl on StartPage the problem reproduced on C# file child frame just the same.
NONonExistoMay 10, 2005 01:40 AM
By the way. I asked my friend to reproduce this issue on his machine.
It been reproduced on w2K3+SP1 just the same way.
ADAdministrator Syncfusion Team May 10, 2005 04:11 PM
Thanks for your feedback. This is a known shortcoming in the XPMenus framework in v18.104.22.168 and we have an open bug report defect# 259 on this :
Defect #259 - Keyboard navigation disabled in XPMenus
We will try our very best to address this issue at the earliest. We appreciate your feedback, and thanks for your patience.