Editor Widget in a Persistent Proc.

lee_shelton

New Member
I made some code to display a report to a disk file. Then use an editor widget's read-file method to view it on screen (Character SCO Unix / Progress 8.2c). Worked fine.
Then I placed the code in a persistent procedure to make this available to other reports.

I just copied the code straight over and made the name of the file an input param.

But using the editor widget from within a PP makes the page-up / page-down keys inactive.

Has anyone else seen this before?
Thank you
 

lee_shelton

New Member
Try closing the output before calling the PP. It's not a page-down problem it's that the output is not all there, so there's nothing to 'page-down' to.

If the 'output close' is in the PP (due to the cut/paste), it may not close the output stream of the calling procedure...

use:
output close.
run screen-print in h_tool (input fname).
 
Top