Ticket #495 (Open)Fri Aug 28 03:26:02 UTC 2020
Draw module renders transformed text object incorrectly when using font handle 0
| Reported by: | Chris Hall (132) | Severity: | Normal |
| Part: | RISC OS: Application | Release: | |
| Milestone: | Status | Open |
Details by Chris Hall (132):
The Draw module version 1.41 (25-Apr-2020) and the earlier version 2.27 (09-Jan-2004) both render a transformed text object incorrectly when its font handle is zero.
Example screen shot (www.svrsig.org/drwtst.zip) shows a text object and a transformed text object rendered by ArtWorks (correctly) and by Draw (incorrectly).
Changelog:
Modified by Sprow (202) Mon, August 31 2020 - 14:17:05 GMT
- Part changed from Unspecified to RISC OS: Application
If by “font handle is zero” you mean the system font, then this is expected. See PRM 5a-521, which gives details of the differences in handling transformed text between the Drawfile module and !Draw, and hence you can deduce what !Draw will do. Or, put another way, take a look which adjuster handles there are on a line of system font in !Draw.
If you want transformed system font you must use System.Fixed or System.Medium which go via Font Manager and therefore can be transformed.
Modified by Chris Hall (132) Wed, September 09 2020 - 07:20:12 GMT
PRM 4-460 (describing text object type 1) says the font number is the index of the font table name list except when it is zero when it is ‘a system font that is sure to be present’. Page 4-468 (describing transformed text objects type 12) says that theremaining fields are exactly as specified for text objects.
The !Draw application is not relevant to this bug, only the Draw module.
