New method when 'no-cancel' is desired¶

What is new - 8.2¶

In DataFlex Reports, the report engine (OCX) is responsible for tasks such as reading data, formatting pages, and generating a report. While the engine is busy with these tasks, the application may not be able to respond to Windows messages, including requests to check if the application is still running or if the user wants to abort the report formatting.

To address this issue, DataFlex Reports previously emptied the message queue. However, this approach had its own limitations, including users initiating other actions - such as clicking on buttons and using timers - during report generation. Developers should be aware of this and block users from clicking on buttons by setting the enabled_state of these controls. Timers should be suspended as well.

Because it is not always necessary to respond to Windows messages, the default behavior has been changed in the 8.2 release. Now, if the ability to cancel a report from a status panel is not required, the message queue is not emptied. This automatically prevents users from initiating other actions while a report is being generated.

To revert to the previous behavior, where the message queue is emptied and users can cancel a report from a status panel, the new pbReportNoCancel property can be set to "false".