---
title: "Programming tips, part 2"
type: "article"
slug: "programming-tips-part-2"
url: "http://localhost/article/programming-tips-part-2/"
markdown_url: "http://localhost/article/programming-tips-part-2.md"
published_at: "2021-02-07T16:29:05+00:00"
modified_at: "2026-07-29T10:07:01+00:00"
featured_image:
  url: "http://localhost/wp-content/uploads/2022/04/20230809-041332.jpg"
excerpt: "The statements in \"Programming tips, part 2\" apply to the 2068 as WELL. However, at additional tip for the long PRINT statement is the use of the print apostrophe, which moves the print position to the beginning of the next line regardless of the previous print position. The statement \"Programming tips, part 2\" can be…"
category:
  - name: "Hampton Roads T/S User Group Newsletter"
    slug: "hampton-roads-t-s-user-group-newsletter"
    taxonomy: "category"
    url: "http://localhost/category/periodicals/hampton-roads-t-s-user-group-newsletter/"
post_tag:
  - name: "Best of Timex/Sinclair 2068 Articles and Documents"
    slug: "ts2068best"
    taxonomy: "post_tag"
    url: "http://localhost/tag/ts2068best/"
  - name: "TS 2068"
    slug: "ts2068"
    taxonomy: "post_tag"
    url: "http://localhost/tag/ts2068/"
model:
  - name: "Timex/Sinclair 2068"
    slug: "ts-2068"
    taxonomy: "model"
    url: "http://localhost/model/ts-2068/"
indiv:
  - name: "Edwin Krampitz"
    slug: "edwin-krampitz"
    taxonomy: "indiv"
    url: "http://localhost/indiv/edwin-krampitz/"
publication: "Hampton Roads T/S User Group Newsletter"
publication_r:
  id: 28013
  title: "Hampton Roads T/S User Group Newsletter"
  type: "periodical"
  url: "http://localhost/periodical/hampton-roads-t-s-user-group-newsletter/"
authors: "Edwin Krampitz"
authors_r:
  - name: "Edwin Krampitz"
    slug: "edwin-krampitz"
    taxonomy: "indiv"
    url: "http://localhost/indiv/edwin-krampitz/"
volume: "1"
issue: "8"
issues_articles:
  - id: 47389
    title: "Hampton Roads T/S User Group Newsletter"
    type: "issue"
    url: "http://localhost/issue/hampton-roads-t-s-user-group-newsletter/"
pages: "5-7"
pubdate: "October 1985"
archive_link: false
volumeissue: "v1n8"
---

# Programming tips, part 2

The statements in “Programming tips, part 2” apply to the 2068 as WELL. However, at additional tip for the long PRINT statement is the use of the print apostrophe, which moves the print position to the beginning of the next line regardless of the previous print position. The statement “Programming tips, part 2” can be replaced on the 2068 with this:

```
3005 PRINT TAB 10; "BATTLESHIPS";TAB 10;"----------";AT 3,0;"SET UP YOUR SHIPS ON THE TOPHALF OF THE SCREEN."''"ALL COORDINATES SHOULD BE IN THEFORM: LETTER FOLLOWED BY NUMBER."''
```

There seEms to be a lot of confusion regarding use of attributes in and out of PRINT statements. To put it simply, PAPER, INK, FLASH, etc., affect the whole SCREEN when used as separate statements. For example:

```
1000 PAPER 4: INK 6
```

will make the whole screen green and the color of the print yellow — not exactly a beautiful combination. If used in a PRINT statement like this:

```
1000 PRINT PAPER 4; INK 6;"Green paper, yellow ink"
```

will only make the words following it have those attributes. The rest of the screen will remain whatever PAPER and INK colors it had before, and subsequent PRINT statements, unless attributes are defined in the statement itself as here, will have the same colors as the screen. The same conditions apply to INVERSE, BRIGHT, and FLASH.