Page 1 of 1

GDI Resources

Posted: Fri Aug 07, 2009 11:26 am
by ConvertFromOldNGs
by synergyfocus >> Tue, 11 Dec 2001 20:53:58 GMT

Re: GDI Resources

Posted: Fri Aug 07, 2009 11:26 am
by ConvertFromOldNGs
by CarlRanson >> Tue, 11 Dec 2001 21:19:00 GMT

I would query JadeSupport on what constitutes a "quite moment in processing".

Its possible that they mean that the program gets back into it's main message loop, in which case you can probably force it with a call to doWindowEvents after each report.

Cheers,
CR

Re: GDI Resources

Posted: Fri Aug 07, 2009 11:26 am
by ConvertFromOldNGs
by synergyfocus >> Tue, 11 Dec 2001 21:29:28 GMT

Tried that - no joy.
Also tried a process.sleep - no joy.

Re: GDI Resources

Posted: Fri Aug 07, 2009 11:26 am
by ConvertFromOldNGs
by saleslegend >> Wed, 12 Dec 2001 3:14:26 GMT

Have you tried using createPrintForm ?

Just use :
form := FrmRLPrint.createPrintForm;

Instead of the usual :
create form;


Cheers Kelvin Lister
Genztech 2001 Limited.

Re: GDI Resources

Posted: Fri Aug 07, 2009 11:26 am
by ConvertFromOldNGs
by cnwkpd1 >> Thu, 13 Dec 2001 23:55:59 GMT

createPrintForm is what you need. We had exactly the same issue in Jasper with a job that created an arbitrary number of report forms. You don't have any control over when JADE decides to get in and clean up the Windows resources, so the only way to get around the issue is not to use them.

We did find a couple of issues with the behaviour of some controls on a form created with createPrintForm - one was that TextBox::lineCount didn't work (fixed in 5.1.10.66) and another was an issue where attempting to reset the value of the TextBox text property back to it's original value in Painter after it had been changed at runtime didn't work (patched in 5.1.10.158)

Good luck.
Kevin Douglas, Jasper