Roger,
Have a user that wants a child window open when we are doing a particular internet request to have a standard button to click only when its done. Right now it runs with a please wait, then gives them their message, usually 5-10 seconds. Not necessary to get into the details on why, but just wanted to see if there is a method to do it..have a WHEN on the button and update it either when the soap request is done, or in 15 seconds if there is a delay in the response.
Any suggestions?
Fred
Omni
Substitute for cDialog
-
Cliff Wiernik
- Posts: 605
- Joined: Thu Jan 28, 2010 9:11 pm
- Location: Steven Point, Wisconsin USA
- Contact:
Re: Substitute for cDialog
I do something like this in several processing applications I have.
I have a first dialog that opens. It would have a flag for the object you want to modify. I then do the process by starting a second thread and pass the getlist and variable to the 2nd thread. Because of the passing of the variables, they are accessible in the spawned thread and can be updated and seen in the first dialog. Within the 2nd dialog, I may be processing a loop. Normally, when that is happening, you cannot click on items in the first dialog. In this case, since they are different threads, you can access the first thread, click say a cancel button, which is seen and available in the 2nd thread and you can operate using this value to for instance exit out the the 2nd thread. The eliminates the need to use something like dc_appevent() which did not work as well. This approach can be expanded I think to do what you want to do, have something in the 2nd thread update information in the first thread.
I have a first dialog that opens. It would have a flag for the object you want to modify. I then do the process by starting a second thread and pass the getlist and variable to the 2nd thread. Because of the passing of the variables, they are accessible in the spawned thread and can be updated and seen in the first dialog. Within the 2nd dialog, I may be processing a loop. Normally, when that is happening, you cannot click on items in the first dialog. In this case, since they are different threads, you can access the first thread, click say a cancel button, which is seen and available in the 2nd thread and you can operate using this value to for instance exit out the the 2nd thread. The eliminates the need to use something like dc_appevent() which did not work as well. This approach can be expanded I think to do what you want to do, have something in the 2nd thread update information in the first thread.