James, please try this example...
Júlio César M. Ferreira
FWH 8.10 / xHB 1.1.0 / xDevStudio 0.72 / Pelles C 5.0.1 / SQLLIB 1.9
James, please try this example...
Julio,
I downloaded it twice and both times I am getting an "invalid or corrupted zip file" message. Please create a new zip and just email me a copy.
James
James Bott wrote:Julio,
I downloaded it twice and both times I am getting an "invalid or corrupted zip file" message. Please create a new zip and just email me a copy.
James
#Include "FiveWin.Ch"
FUNCTION Main()
LOCAL oWnd, lInit:=.T., oDlg, oSay, cSay
cSay:="Loading, please wait..."
DEFINE DIALOG oDlg FROM 0, 0 TO 5,40
@ 1, 1 SAY oSay PROMPT cSay CENTERED
ACTIVATE DIALOG oDlg NOWAIT CENTERED
SysRefresh()
WaitSeconds(2)
DEFINE WINDOW oWnd
ACTIVATE WINDOW oWnd MAXIMIZED;
ON PAINT Paint_Window(oDlg,@lInit) ;
ON INIT Init_Window(oSay,@cSay,oDlg)
RETURN (NIL)
STAT FUNC Init_Window(oSay,cSay,oDlg)
cSay:="Init process, wait..."
oSay:Refresh()
WaitSeconds(3)
cSay:="Ready!"
oSay:Refresh()
MsgBeep()
WaitSeconds(1)
oDlg:End()
RETURN (NIL)
STAT FUNC Paint_Window(oDlg,lInit)
IF lInit
oDlg:SetFocus()
SysRefresh()
CursorWait()
lInit:=.F.
ENDIF
RETURN (NIL)Julio,
Ok, I tried your example, but I still don't know what you are trying to do and/or what problem you are having.
Is the program you sent showing a problem? If so, what is the problem?
Or, is it working the way you want.
I think you should also rethink having so many windows popping up. A better design is to put messages in the same window where they apply. You can also either use the hourglass cursor for short waits (up to about 5 seconds) or a progress bar for longer waits when you can calculate the total wait time or an animation if you don't know the total wait time.
Did you try my example showing the updated message on the main window?
James
Julio,
Why do have the MS-DOS window open. Do your users always have a DOS app running, or is it just a problem with the DOS window that you noticed because you have one open when programming?
Most users never run DOS apps anymore, so if there is a problem with a DOS window I don't think your users will ever see it.
James
FUNCTION waitDlg( oDlg, oWnd )
LOCAL oSay
DEFINE DIALOG oDlg OF oWndJulio,
I see that you are opening a window then a dialog, then another dialog. Why do you need two dialogs? Can't you just close the first dialog when you open the second one?
Are you updating a customer browse in the main window, or in the first dialog?
I think a redesign of the interface would probably be a better solution.
James
James Bott wrote:Julio,
I see that you are opening a window then a dialog, then another dialog. Why do you need two dialogs? Can't you just close the first dialog when you open the second one?
Are you updating a customer browse in the main window, or in the first dialog?
I think a redesign of the interface would probably be a better solution.
James
James Bott wrote:Julio,
Good. I highly recommend getting a copy of the book, "About Face 2.0: The Essentials of Interaction Design"
http://www.amazon.com/About-Face-2-0-Essentials-Interaction/dp/0764526413/ref=sip_rech_dp_10
You can get a used copy for less than US$5.
There is a newer version but it discusses more about web design, so I recommend getting the 2.0 version.
James