They appear to queue up and after all are done SAM_ReportFinish is invoked as many times as there are reports.
The whole purpose of SAM_ReportFinish is defeated here. It's almost like queueing up SAM_Close messages...I would like to update you on the issue you have raised.
There is following description in source code : Notify the user's app, by posting a SAM_ReportFinish message. We are posting the message here instead of sending it directly because we need to allow RDW to complete destroying the report window.
So, SAM_ReportFinish is posted not sent, and we cannot change this behavior because this behavior has not been changed from 4.2 and changing this behavior might break existing application.
For this there is an option you can enable SalYield to check queued messages while executing long operation SAL code.
Is SAM_ReportFinish of any use now?
Who is online
Users browsing this forum: [Ccbot] and 0 guests