FiveTech Software tech support forums

There is no need to switch workareas.
XBrowse has nothing to do with currently selected workarea.

If you still have any problem, please provide a small sample.

Yes, I'm sure of that because the aliases are generated by the program. So, what do you suggest for switching the workarea on focus change? Please note that bGotFocus seems not to be enough.

EMG

Can it be done?

Can be done, as long as you programmatically ensure that you are not creating a new Xbrowse for the same alias for which you already created another Xbrowse.

Yes, I'm using different workareas. But the browses are dinamically created so I can't use any alias, I need that the current workarea is the one of the browse with the focus.

Can it be done?

EMG

I assume you are using different workareas for different browses. We can not use same workarea in different xbrowses. Switching the xbrowses does not switch workareas (does not change the selected workarea). XBrowse is also not affected by the currently selected workarea. XBrowse reads from oBrw:cAl...

Yes, I already add

ALIAS ALIAS()

Is it correct? But the problem is that the workarea become number zero when I switch to another dialog with another XBrowse.

EMG

Dear Enrico,

I'm so sorry to ask you.
Do you add "ALIAS" in XBROWSE command? If not, I guess the XBROWSE will read from current workarea.

Is there any code in XBrowse that changes the current workarea? Otherwise, who is that selects the workarea number zero? I don't do it for sure.

EMG

Sorry, it doesn't solve the problem. There are some codeblocks in XBrowse that are evaluated before bPainted and bGotFocus, so before workarea setting.

EMG

And try with ?

Code: Select all  Expand view

oBrw:bpainted = { || dbSelectArea( "dbffile" )}

Yes, same problem. oDlg:bGotFocus doesn't start at all.

EMG

Enrico, have you tried with oDlg:bGotFocus = { || dbSelectArea( "dbffile" )} .
Best regards
Otto

I'm having strange problems with XBrowse and nomodal dialogs. Switching from one dialog to another, often I find 0 (zero) as the current workarea. What is the correct way to manage workarea switching in such scenario? I'm currently using oBrw:bGotFocus ...

nageswaragunupudi wrote:Please reproduce the error.log.
Do you have the problem in mdi-dialog only or in normal dialogs also?

Any solution?

Hi Mr.Rao Look it. not work=> Child Window+Resource Dialog( ACTIVATE DIALOG ::oDlg NOWAIT ) https://i.postimg.cc/yYr2vrsg/MDI-bug1.gif Work OK=> Child Window+Resource Dialog( ACTIVATE DIALOG ::oDlg NOWAIT ) and I Open another Resource Dialog for New/Edit data https://i....