|Anonymous | Login||10-27-2020 12:54 UTC|
|Main | My View | View Issues | Change Log | Docs|
|Viewing Issue Advanced Details [ Jump to Notes ]||[ View Simple ] [ Issue History ] [ Print ]|
|ID||Category||Severity||Reproducibility||Date Submitted||Last Update|
|0006703||[Squeak] Graphics||major||always||10-03-07 05:44||07-24-08 01:58|
|ETA||none||Fixed in Version||Product Version||3.10|
|Summary||0006703: In sq7143 bolding an Accuny font produces noticable glitch for space. Other font weirdness too.|
For this one:
In a fresh 7143
Select some text in the Scroll window.
Type in succession
Cmd-1 (text becomes 9 pt)
Cmd-2 (text becomes bigger)
Cmd-3) (bigger still)
Cmd-4 (text becomes 24 pt and is rendered as bold. All spaces have visible glitches in there lower parts.)
Cmd-5 (text remains 24-pt but now has normal emphasis.)
Playing around with other text modifing command keys shows other problems.
In general bolding any large size of Accuny will produce noticable glitches in the space character. The glitches get smaller as the font does disappearing when we get down to 12 point. The glitches are always in the lower portion of the character.
|Steps To Reproduce|
The reason for this report is to note a reproducible test that exposes the bugs.
And to note that it is still a current problem in the 3.10 system.
It will be interesting to see if either of them persist past the next changes and patches to fonts.
world>help>command key help
(not available on all platforms)
Cmd-1 10 point font
Cmd-2 12 point font
Cmd-3 18 point font
Cmd-4 24 point font
Cmd-5 36 point font
Cmd-6 color, action-on-click, link to class comment, link to method, url
Brings up a menu. To remove these properties, select
more than the active part and then use command-0.
Cmd-9 narrow (same as negative kern)
Cmd-0 plain text (resets all emphasis)
Cmd-- underlined (toggles it)
Cmd-= struck out (toggles it)
From this description Cmd-4 should produce regular 24 point not bold. So thats one bug. Whats going on there?
And of course bolding is not suppose to glitch up the space character. So thats a second bug. This one is described in mantis 0003604
Side note: I am running os9.1 on a g3 imac. And while playing with the variations of command keys above I've managed to get the program to quit and the system to crash shortly there after.
Now that might be random or due to other causes. But this is not the only time I have had a mysterious crash while in squeak so I am also suspicious that the font irregularities may trigger a more serious bug in the system. I have no idea what reproduces this error and am somewhat reluctant to chase it. But the question for the font bugs is do they have a possibility of exhausting memory?
Yours in curiosity and service, --Jerome Peace
(0012406 - 346 - 380 - 380 - 380 - 380 - 380)
edited on: 07-24-08 01:59
Bolding uses a bonk form to clear out bits between glyphs. The form is fixed at 1@16 so it fails to work on large fonts.
The glitch in spaces come from the use of big boxes for all unprintable characters. So the character after a space is a box when it gets bolded only part of it will be bonked out ot fhe space glyph. And problems ensue.
|10-03-07 05:44||wiz||New Issue|
|10-03-07 05:44||wiz||Status||new => assigned|
|10-03-07 05:44||wiz||Assigned To||=> andreas|
|10-03-07 05:45||wiz||Relationship added||child of 0006570|
|10-03-07 05:45||wiz||Relationship added||related to 0003604|
|07-24-08 01:58||wiz||Note Added: 0012406|
|07-24-08 01:59||wiz||Note Edited: 0012406|
| Mantis 1.0.8[^]
Copyright © 2000 - 2007 Mantis Group
47 total queries executed.|
34 unique queries executed.