Unable to block wait for asynchronous request to complete (without processing other events)? - Progress Community

Loading

Skip to Main Content

Unable to block wait for asynchronous request to complete (without processing other events)?

Unable to block wait for asynchronous request to complete (without processing other events)? This article describes the problem with WAIT-FOR async and a workaround to get rid of such situation.

Jun 7, 2022
Knowledge

Title

Unable to block wait for asynchronous request to complete (without processing other events)?

URL Name

unable-to-block-wait-for-asynchronous-request-to-complete-without-processing-other-events

Article Number

000214836

Environment

Product: OpenEdge Version: 11.7.x OS: All supported platforms

Question/Problem Description

Unable to block wait for asynchronous request to complete (without processing other events)?
Writing a 'WAIT-FOR PROCEDURE-COMPLETE OF async-handle-var' statement causes not only the procedure-complete event to be processed while waiting but every other possible event as well, like the user closing the window and no blocking way to only continue execution of the PROCEDURE-COMPLETE event and not react to any other possible events.

Steps to Reproduce

- Download the attached zip and extract - Run "TestClient.w" located in "000214836-Repro" directory on AppServer

Clarifying Information

Error Message

Defect Number

Enhancement Number

OPENEDGE-I-1034

Cause

Resolution

A new enhancement request has been created and until the feature is available, use the workaround below. It was determined that the Progress Product is functioning as designed.

An enhancement request has been submitted as an Idea on the Progress Community. To promote the Idea, click on this link: https://openedge.ideas.aha.io/ideas/OPENEDGE-I-1034 Customer feedback is valuable and Idea submissions are monitored by our Product Management team. Enhancement requests are reviewed during the planning phase of each new product release and a list of the enhancements chosen for implementation can be found in the Release Notes documents that accompany each release. Once an Idea is submitted the Progress Software Community will have the opportunity to comment on and vote for the Idea. It's priority will be evaluated as customer demand weighs in through Article Feedback and through vote count in the Ideas Portal

For detailed information on how to submit an Idea, please refer to the Knowledge Base article How to submit an idea for a Progress product enhancement.

Workaround

Walk the window chain (starting at SESSION:FIRST-CHILD) and the form chain (SESSION:FIRST-FORM) to disable all other classic and .NET UI, you can find this simple routine in the directory "000214836 Workaround"
(or)
Display a dialog box, which prevents any other UI from receiving user interaction, until the async request completes.

Notes

Keyword Phrase

Last Modified Date

6/7/2022 12:38 PM

OpenEdge General DiscussionsOpenEdge DeploymentOpenEdge DevelopmentOpenEdge RDBMSOpenEdge ArchitectureOpenEdge Pro2

Drop Files

Upload FilesOr drop files

000214836
000214836
May 10, 2022
7KB
zip

Disclaimer

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.

Loading

Unable to block wait for asynchronous request to complete (without processing other events)? - Progress Community