- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
When I use DLGFLUSH in a CALLBACK-Routine only Buttons are updated, no edit boxes. It makes no differences, whether
I use .TRUE. in DLGFLUSH, whether the edit boxes are changed, whether I use DLGSETSUB for the edit box. Can anybody
help me.
I use .TRUE. in DLGFLUSH, whether the edit boxes are changed, whether I use DLGSETSUB for the edit box. Can anybody
help me.
コピーされたリンク
1 返信
- 新着としてマーク
- ブックマーク
- 購読
- ミュート
- RSS フィードを購読する
- ハイライト
- 印刷
- 不適切なコンテンツを報告
Hi,
Below is the explanation from the DLGFLUSH documentation.
Regards,
Leo
However, there may be cases where you want to change a control outside of a dialog callback, or from within a loop in a dialog callback. In these cases, DLGFLUSH is required, but not always sufficient, to update the dialog display. DLGFLUSH sends pending Windows system messages to the dialog box and the controls that it contains. However, many display changes do not appear until after the program reads and processes the messages that the Windows system has sent to the program as the result of the messages sent by DLGFLUSH. A loop that processes the pending messages is often required; for example:
use DFWINTY
use USER32
logical lNotQuit, lret
integer iret
TYPE (T_MSG) mesg
lNotQuit = .TRUE.
do while (lNotQuit .AND. (PeekMessage(mesg, 0, 0, 0, PM_NOREMOVE) <> 0))
lNotQuit = GetMessage(mesg, NULL, 0, 0)
if (lNotQuit) then
if (DLGISDLGMESSAGE(mesg) .EQV. .FALSE) then
lret = TranslateMessage(mesg)
iret = DispatchMessage(mesg)
end if
end if
end do
Below is the explanation from the DLGFLUSH documentation.
Regards,
Leo
However, there may be cases where you want to change a control outside of a dialog callback, or from within a loop in a dialog callback. In these cases, DLGFLUSH is required, but not always sufficient, to update the dialog display. DLGFLUSH sends pending Windows system messages to the dialog box and the controls that it contains. However, many display changes do not appear until after the program reads and processes the messages that the Windows system has sent to the program as the result of the messages sent by DLGFLUSH. A loop that processes the pending messages is often required; for example:
use DFWINTY
use USER32
logical lNotQuit, lret
integer iret
TYPE (T_MSG) mesg
lNotQuit = .TRUE.
do while (lNotQuit .AND. (PeekMessage(mesg, 0, 0, 0, PM_NOREMOVE) <> 0))
lNotQuit = GetMessage(mesg, NULL, 0, 0)
if (lNotQuit) then
if (DLGISDLGMESSAGE(mesg) .EQV. .FALSE) then
lret = TranslateMessage(mesg)
iret = DispatchMessage(mesg)
end if
end if
end do