godzil/MB701-Reverse
1
0
Fork 0
mirror of https://github.com/Godzil/MB701-Reverse.git synced 2025-12-12 18:08:54 +01:00
Code Issues Packages Projects Releases Wiki Activity

Fix typos in PTCR.md

Browse Source
This commit is contained in:
Manoël Trapier 2023-06-08 16:02:34 +01:00 committed by GitHub
parent d60109a737
commit d03f389407
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 15 additions and 15 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

28
PTCR.md
View File

@ -81,7 +81,7 @@ A line is drawn between [x0;y0] and [x1; y1]
|--------|-----------|-----------|--------|--------|--------|--------| ------ | |--------|-----------|-----------|--------|--------|--------|--------| ------ |
| F2 | Stroke #1 | Stroke #2 | ??? | x0 | y0 | x1 | y1 | | F2 | Stroke #1 | Stroke #2 | ??? | x0 | y0 | x1 | y1 |
The circle is drawn in the rectangle designed by [x0;y0] - [x1; y1] The circle is drawn in the rectangle defined by [x0;y0] - [x1; y1]
#### Examples: #### Examples:
- `F2 0A 55 02 34 24 54 44` - `F2 0A 55 02 34 24 54 44`
@ -120,7 +120,7 @@ So if you read 28, the actual color to use is 0
|--------|-----------|-----------|------------------------| |--------|-----------|-----------|------------------------|
| F7 | Stroke #1 | Stroke #2 | ??? (Color to clear?) | | F7 | Stroke #1 | Stroke #2 | ??? (Color to clear?) |
Code clear the canvas to all white whatever the value. Not sure what the byte 3 is suppose to represent. Clear the canvas to all white whatever the value. Not sure what the byte 3 is suppose to represent.
#### Examples: #### Examples:
- `F7 0C 4B 00` - `F7 0C 4B 00`
@ -177,7 +177,7 @@ _If the value is not 0 (16x16), 1 (24x24) or 2 (32x32) it will default back to 0
## How stroke number work: ## How stroke number work:
For some reason 0 is represented by 0x0A (10) 0x0A. For some reason 0 is represented by 0x0A (10) 0x0A.
When the number of storke is increased the second byte is incremented by 1. When the number of stroke is increased the second byte is incremented by 1.
Then when the second byte reach 0x9F (159) the first one will be incremented and the Then when the second byte reach 0x9F (159) the first one will be incremented and the
second byte reset to 0x0A. second byte reset to 0x0A.
@ -185,16 +185,16 @@ second byte reset to 0x0A.
Example: Example:
| Hex | Binary | Decilam | | Hex | Binary | Decimal | Value |
|-------|---------------------|---------| |-------|---------------------|---------|-------|
| 0A 0A | 0000 1010 0000 1010 | 10 10 | | 0A 0A | 0000 1010 0000 1010 | 10 10 | 0 |
| ... | | | | ... | | | |
| 0A 9F | 0000 1010 1001 1111 | 10 159 | | 0A 9F | 0000 1010 1001 1111 | 10 159 | 149 |
| 0B 0A | 0000 1011 0000 1010 | 11 10 | | 0B 0A | 0000 1011 0000 1010 | 11 10 | 150 |
| ... | | | | ... | | | |
| 0B 9F | 0000 1011 1001 1111 | 11 159 | | 0B 9F | 0000 1011 1001 1111 | 11 159 | 299 |
| 0C 0A | 0000 1100 0000 1010 | 12 10 | | 0C 0A | 0000 1100 0000 1010 | 12 10 | 300 |
| ... | | | | ... | | | |
| 18 89 | 0001 1000 1000 1001 | 24 137 | | 18 89 | 0001 1000 1000 1001 | 24 137 | 3727 |
_Why does it work this way? Your guess is as good as mine._ _Why does it work this way? Your guess is as good as mine._