Hourglass cursor while waiting for long report to build a preview?

hsm

There must be a simple solution to providing the user with a 'please wait' indication, given how long some reports will take to build before a preview is available.
How is it done?

In delphi, if I write

screen.Cursor := crHourglass;
 frxReport1.ShowReport(true);
 screen.Cursor := crDefault;

then nothing seems to happen as I believe the report immediately re-sets the cursor to a hand shape, so that's what you see hovering over a blank page while the report is building all its pages.

Are there events I can use that detect the start of the report loading its data and the end of the last page being built so I can show an hourglass to the user during the creation of a long report? And if so, how do you refer to the screen cursor inside the code page of the report?

I did ask this a long time ago but never had any replies.

(I don't want to modify the FDefaultCursor value in the source code of frxPreview.pas as some of my reports manipulate that for other reasons. Besides, I only want the hourglass up to the point when the last page has been built )

(originally posted in Fastreports.net by mistake)

gordk

try changing the oldstyle progress setting of the tfrxreport component from false to true.
this might help you out.

hsm

gordk wrote: »

try changing the oldstyle progress setting of the tfrxreport component from false to true.
this might help you out.

Thanks gordk,
That is just as good, if not better, than having the hourglass cursor as the user does not expect to see the report until it appears and its obvious that is being built.

I had no idea what that property did.
Is there anywhere a complete list of the properties and events of reports and the objects you can put on a report, together with a description of what they do?
I often find I get a very useful reply to a forum question (usually from you or gpi) telling me to use such and such event or this or that property but I wonder how they know.
Apart from the rather basic things mentioned in the user, programmer or developer manuals the rest seems to be guesswork or trial and error.

gordk

some unfortunately are trial and error, there are a number of things that can be found in the changes text files as well, IIRC the old style progress was added way back when changing from fr2 to fr3.