Project

General

Profile

Bug #402

Chr$(8), Chr$(9), Chr$(10), Chr$(12),Chr$(13) are not processed properly in AOZ.

Added by Brian Flanagan over 3 years ago. Updated about 2 years ago.

Status:
Closed
Priority:
High
Assignee:
Target version:
-
Start date:
06/28/2020
Due date:
% Done:

0%

Estimated time:
2:00 h
Affected version:

Description

This is what SHOULD happen when these special characters are contained within strings being printed:

Chr$(8) (backspace) should put the text cursor at the previous x position.
Chr$(9) (tab) should put the text cursor at the next TAB position.
Chr$(10) (line feed) should put the text cursor at the current x position on the next line.
Chr$(12) (form feed) should have the same effect on-screen as Chr$(13).
Chr$(13) (carriage return) should put the text cursor at the beginning of the current line.

Right now, all of these are ignored.

#1

Updated by Brian Flanagan over 3 years ago

  • Assignee set to AOZ Studio Team
  • Estimated time set to 2:00 h
  • Affected version changed from 0.9.9.3 to Beta RC2

Tab (Chr$(9)) is now working, but the rest still fail.

Chr$(8), Chr$(10), and Chr$(12) move the cursor forward 1.
Chr$(13) does nothing.

#2

Updated by Brian Flanagan over 3 years ago

  • Priority changed from Normal to High
#3

Updated by malcolm harvey about 3 years ago

  • Affected version changed from Beta RC2 to 1.0.0 (B4)

Brian Flanagan wrote:

This is what SHOULD happen when these special characters are contained within strings being printed:

Chr$(8) (backspace) should put the text cursor at the previous x position.
Chr$(9) (tab) should put the text cursor at the next TAB position.
Chr$(10) (line feed) should put the text cursor at the current x position on the next line.
Chr$(12) (form feed) should have the same effect on-screen as Chr$(13).
Chr$(13) (carriage return) should put the text cursor at the beginning of the current line.

Right now, all of these are ignored.

Tested this again 2/3/21 and still not working.
ie: For example, in relation to just the chr$(13) and chr$(10).

Still in Amiga mode, Chr$(13); will only do CR, and Chr$(10); will only do LF

#4

Updated by malcolm harvey about 3 years ago

A real world example of this on an input char routine.

Ok, When I detect how far using the text curs moves with X curs in my case 19 characters, I then decide to move down a line, so I do a print chr$(13) or and in combination with a print chr$(10) which moves the curs down left to start as it should and down a line.
What happens then is, the next character input again jumps back to the end of the previous line and then, the next char goes back to the start of the next line as it should again.
The Curs in Amiga mode anyways, does not actually go there at all at this point in time in reality.

#5

Updated by Brian Flanagan over 2 years ago

  • Affected version changed from 1.0.0 (B4) to 1.0.0 (B10) u16

Re-tested in 1.0.0 (B10) u16
Tab is still the only one of these working.

Chr$(9) is working.
Chr$(8) fails. (ignored)
Chr$(13) fails. (ignored)
Chr$(10) fails. (ignored)
Chr$(12) fails. (ignored)

#6

Updated by Brian Flanagan over 2 years ago

Failures are in both manifests.

#7

Updated by Brian Flanagan over 2 years ago

Re-tested in 21 Oct 2021 version.
Chr$(9) is still the only one that works.

#8

Updated by David Baldwin over 2 years ago

  • Status changed from New to Resolved
  • Assignee changed from AOZ Studio Team to David Baldwin

All fixed.

#9

Updated by Brian Flanagan over 2 years ago

  • Status changed from Resolved to Feedback

Almost. Sorry about the error in the bug report. (My bad.)

Chr$(12) should NOT have the same effect as Chr$(13)
It should place the text cursor at the top left of the current text window.

  • Brian
#10

Updated by David Baldwin over 2 years ago

  • Status changed from Feedback to Resolved

Fixed

#11

Updated by David Baldwin about 2 years ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF