Skip to main content

Passing TAB key to .Net assembly

  • February 8, 2011
  • 4 replies
  • 0 views

[Migrated content. Thread originally posted on 07 February 2011]

I have a .Net assembly that contains a WebBrowser control. When this assembly is on a Cobol form the tab key is trapped by the Cobol form and activates the next control in tab order. I need the TAB key to be passed to the assembly to move through text fields on the WebBrowser control. When the assembly is placed on a .Net form it performs as expected, with the TAB key being passed to the WebBrowser control.

I'm using the 8.1 runtime.

4 replies

[Migrated content. Thread originally posted on 07 February 2011]

I have a .Net assembly that contains a WebBrowser control. When this assembly is on a Cobol form the tab key is trapped by the Cobol form and activates the next control in tab order. I need the TAB key to be passed to the assembly to move through text fields on the WebBrowser control. When the assembly is placed on a .Net form it performs as expected, with the TAB key being passed to the WebBrowser control.

I'm using the 8.1 runtime.
navigation keys are normally managed by the runtime itself. If your net control has focus, and does handle tabs, it should be able to process it. You might want to check your TAB/NO-TAB use in screen section (see documentation).

I vaguely remember there was an issue some time ago with controls and navigation keys, not sure if this applies here though. But if you have a chance to test this using version 9.0, it migth be worth doing that.

If the problem persists, I suggest you contact techhnical support with a small example reproducing the problem.

[Migrated content. Thread originally posted on 07 February 2011]

I have a .Net assembly that contains a WebBrowser control. When this assembly is on a Cobol form the tab key is trapped by the Cobol form and activates the next control in tab order. I need the TAB key to be passed to the assembly to move through text fields on the WebBrowser control. When the assembly is placed on a .Net form it performs as expected, with the TAB key being passed to the WebBrowser control.

I'm using the 8.1 runtime.
I believe it may be the 8.1 runtime. I have requested the 9.0 runtime and am waiting on a response. To further test, I created a simple .Net assembly with 7 text boxes in sequential tab order. When placed on a Cobol window, the cursor begins in the first text box as it should. The TAB key moves the cursor in the following order: 1 to 7, 7 to 5, 5 to 6, 6 to 1, and then it repeats this order. This assembly, when placed in a VB.Net form or when debugging, tabs correctly.

[Migrated content. Thread originally posted on 07 February 2011]

I have a .Net assembly that contains a WebBrowser control. When this assembly is on a Cobol form the tab key is trapped by the Cobol form and activates the next control in tab order. I need the TAB key to be passed to the assembly to move through text fields on the WebBrowser control. When the assembly is placed on a .Net form it performs as expected, with the TAB key being passed to the WebBrowser control.

I'm using the 8.1 runtime.
Try it with 9.0, and if proves the same behavior, raise the topic with tech support.

[Migrated content. Thread originally posted on 07 February 2011]

I have a .Net assembly that contains a WebBrowser control. When this assembly is on a Cobol form the tab key is trapped by the Cobol form and activates the next control in tab order. I need the TAB key to be passed to the assembly to move through text fields on the WebBrowser control. When the assembly is placed on a .Net form it performs as expected, with the TAB key being passed to the WebBrowser control.

I'm using the 8.1 runtime.
I've installed the 9.0 runtime and this is still a problem. I will contact tech support.