FiveTech Software tech support forums

Dear Yuri, Use the WM_ACTIVATE message in the application's main window procedure. This message indicates window activation changes (activating/deactivating). Combine with the LOWORD of wParam to check the activation state (e.g., WA_INACTIVE for background). You may need to inherit a Class ...

Hi Jimmy

REQUEST HB_CODEPAGE_UTF8
HB_CDPSELECT("UTF8")


activating utf8 seems to no longer give error

before it was

REQUEST HB_CODEPAGE_ITWIN
HB_CDPSELECT("ITWIN")

I do not understand excel takes the window setting
TIA

I hide them using the "ON INIT" when activating the dialog. Seemed to work well.

hi,

When we create controls on a dialog, the controls are created only when the dialog is initialized.
So, hWnd is valid only after activating the dialog.

ah ... ok, thx
have to over-think concept

When we create controls on a Window, all controls are fully created and so have valid hWnd.
When we create controls on a dialog, the controls are created only when the dialog is initialized. So, hWnd is valid only after activating the dialog.

... has only one single row. How can I jump directly into edit mode of the first left cell when the dialog opens? I tried the ON INIT clause when activating the dialog. But oBrw:aCols[1]:SetFocus() does of course not work. Anyone who give me a hint?

... but not found. If you have any idea, most welcome. Thanks for your question. Just curious... Why not use the cell content of the browse for activating a action ? You prefer a button action. Is this because the buttons seems to be on top en overlapping the cells ?

Just curious...

Why not use the cell content of the browse for activating a action ?

You prefer a button action. Is this because the buttons seems to be on top en overlapping the cells ?

... created on dialogs, it is no more necessary to use the methods in the on init clause of dialog. It is now possible to use them even before activating the dialog. * TGraph.prg: Fix: DATA lFlat is not initialized in case of Redefine() resulting in runtime error. Fixed. * Enhancement: MENUITEM ...

Add this code to the main window, before activating it.   oWnd:bResized  := <|nType|      local aWnd  := GetAllWin()      if nType == 1         AEval( aWnd, { |o| If( o:ClassName == "TWINDOW" .and. o:hWnd != ...

Add this code to the main window, before activating it.   oWnd:bResized  := <|nType|      local aWnd  := GetAllWin()      if nType == 1         AEval( aWnd, ...

Before activating every child window add this line

Code: Select all  Expand view

oChildWnd:bPostEnd := { || WndMain():oBar:AEvalWhen() }
ACTIVATE WINDOW oChildWnd
 

... Any idea or it's bug? You may be losing it when resizing, but not when moving. The most likely reason is that you are releasing the Icon after Activating the mdichild window like this: ACTIVATE WINDOW oMdiChildRELEASE ICON oIco  Please do not do that. Instead do this: oMdiChild:bPostEnd := ...

... Any idea or it's bug? You may be losing it when resizing, but not when moving. The most likely reason is that you are releasing the Icon after Activating the mdichild window like this: ACTIVATE WINDOW oMdiChildRELEASE ICON oIco  Please do not do that. Instead do this: oMdiChild:bPostEnd ...

... Fixed. * New CLASSDATA bSetup in class TPreview. If assigned, the codeblock is evaluated with oPreview and oWnd as parameters just before activating the preview window. Example Usage: RPrevUserBtns( nil, 2007 ) TPreview():bSetup := <|oPreview, oWnd| WITH OBJECT oWnd:oBar :aControls[ ...