Join The Works program to have access to the most current content, and to be able to ask questions and get answers from Revelation staff and the Revelation community

At 17 MAY 2007 10:40:34AM Colin Kavanagh wrote:

PRINT @(code): @(attribute): @(column,line): expression

per page 131 AREV RBASIC manual

The @codes and @attributes do not work as expected. Colours are off,

@(-11) does note restore the display to normal. I may be wrong but screen seems to change colour of it's own accord when using the PRINT statement.

AREV allowed the ommission of a line variable eg.

       PRINT @(10,10):"NAME":@(20):record:

AREV32 isn't handling this correctly either.


At 17 MAY 2007 11:35AM Colin Kavanagh wrote:

The screen colour change is down to the line number omission.


At 17 MAY 2007 11:43AM Mike Ruane wrote:

Noted.

I'd suspect that the @( number) will be interpereted as a color code. You need the col and row in the print@ statements.


At 18 MAY 2007 05:05AM Colin Kavanagh wrote:

PRINT @(value)

I thought that only the values in sysinclude,print_constants would be interpreted as colour codes and these are all negative. AREV didn't have a problem with just defining a column number, it will assume the current row. We use this throughout 600 routines, it would be a huge job to go through them all and define the row for each print statement.


At 18 MAY 2007 08:12AM Colin Kavanagh wrote:

I notice in the CTO documentation for DO_AT the yparam is optional


At 04 JUN 2007 03:18PM Bryan Shumsky wrote:

Hi, Colin. We now properly support the single (column) parameter for @() positioning in AREV32, just as we have in CTO.

This was a bug in AREV32, and has been fixed for the next release.

Thanks,

- Bryan Shumsky

Revelation Software

View this thread on the Works forum...

  • third_party_content/community/commentary/forums_works/c290a9fab7128883852572de00509e52.txt
  • Last modified: 2023/12/30 11:57
  • by 127.0.0.1