On Init SetFocus Issue

[nageswaragunupudi]

When I have button and wbrowse controls in a dialog, I can not start with the browse focussed even when i use on init browse:setfocus. Here is an example.

Code: Select all  Expand view

FUNCTION BrwFocusTest

   LOCAL oDlg, oBrw, oBtn

   USE CUSTOMER NEW ALIAS CUST

   DEFINE DIALOG oDlg SIZE 200,200 PIXEL

   @ 10,10 BUTTON oBtn PROMPT 'Button' SIZE 40,12 PIXEL OF oDlg

   @ 30,10 LISTBOX oBrw FIELDS ;
         SIZE 80, 60 PIXEL OF oDlg ;
         ALIAS 'CUST'


   oBrw:nClrBackFocus   := CLR_GREEN
   oBrw:nClrForeFocus   := CLR_WHITE

   ACTIVATE DIALOG oDlg CENTER ;
      ON INIT oBrw:SetFocus()

RETURN NIL


I want the browse to get focus when the dialog starts. Despite the ON INIT clause, the focus is on the button.

There are two workarounds though. But I think this should work without workarounds. Can someone help me how to set focus to the browse initially ?

I adopt one of the following two workarounds, but they are workarounds. I guess it should work without any workarounds:

1. After defining the button, oBtn:nStyle -= WS_TABSTOP. Then naturally oBrw is the first control with tabstop and so it gets the focus anyway.

2. Define the browse first and define the button in the subsequent program code. That way browse gets 1st tab stop and button gets the second tabstop despite their appearance.

But I want to focus on the browse initially without disturbing the taborders of the controls. How can I do this please?

[Antonio Linares]

Code: Select all  Expand view

   ACTIVATE DIALOG oDlg CENTER ;
      ON INIT ( oBrw:SetFocus(), .F. )


[Richard Chidiak]

An easy way that always works for me

ODLG:bSTART := { || OBRW:SETFOCUS() }

Hth

Richard

[nageswaragunupudi]

Mr Antonio and Mr Richard

Thank you both very much. Yes both solutions work.

But Mr Antonio, will you kindly enlighten me what magic does this .F. return value do ? Why is it important?

[Antonio Linares]

>
But Mr Antonio, will you kindly enlighten me what magic does this .F. return value do ? Why is it important?
>

It is the way the Windows API has been designed. FWH uses the standard Windows dialogbox procedure. From the Microsoft API docs:

>
The dialog box procedure should return TRUE to direct the system to set the keyboard focus to the control specified by wParam. Otherwise, it should return FALSE to prevent the system from setting the default keyboard focus.
>

[nageswaragunupudi]

Mr Antonio

Thanks for the clarification. Quite educative.