I can report that this now works for me! I also note several things that
were not clear to me from the documentation:
1) the function actually doesn't read the "screen" as displayed but the
screen buffer; in my case it was 80 X 300 so I get 24000 characters from
SysTextScreenRead(0,0)
2) there are no line-end characters in the string - lines shorter than
80 characters are padded with blanks; i.e. the first character of line 2
is at position 81,etc.
I do not consider either of these "bugs" but perhaps the doc's could be
clarified.
Thanks for the quick response and fix!
Gil
On 12/14/2021 3:59 PM, Gilbert Barmwater wrote:
OK, I'll get a new build and validate in my environment. Thanks!
On 12/14/2021 2:04 PM, Rick McGuire wrote:
I just committed a fix for this issue.
Rick
On Tue, Dec 14, 2021 at 11:38 AM Gil Barmwater
<gbarmwa...@alum.rpi.edu> wrote:
Do we have any test for the subject function and are they working as
expected? It seems that when I try "screen =
SysTextScreenRead(0, 0)"
as per the example in the reference, I always get an error 40.1.
However, adding a length as the third argument makes it work.
Gil B.
--
Gil Barmwater
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
_______________________________________________
Oorexx-devel mailing list
Oorexx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-devel
