If I open the context menu for any StringMorph and choose option `change emphasis' ==> Afterwards if I choose option `plain' I obtain error message
"MessageNotUnderstood: plain"
The same applies for all its subclasses (such as ClockMorph)
I tried to figure out the problem and the enclosed change-set is a quick hack solving the problem.
I am using `Squeak3.5-5180.image'
I looked for replies or fixes for this bug, but couldn't find any on BFAV. The bug's still present in my 5707 image so please just ignore this if the bug's already been fixed.
The attached changeset provides a simple fix. It adds TextEmphasis>>plain which just returns self normal.
It might be better to change the context menu to say 'normal' rather than 'plain'. Although I must confess a preference for 'plain'.
frank
<This post brought to you by BFAV2>
but I approved a changeset that fixed all the sender of plain to be substituted by normal. So we do not need to have plain and normal. I do not see the point.
What should be fixed is that some places use number such as 1 2 3 instead of textEmphasis look for the sender of *emphasis:
stef
On 24 févr. 04, at 12:24, frank.shearar@rnid.org.uk wrote:
I looked for replies or fixes for this bug, but couldn't find any on BFAV. The bug's still present in my 5707 image so please just ignore this if the bug's already been fixed.
The attached changeset provides a simple fix. It adds TextEmphasis>>plain which just returns self normal.
It might be better to change the context menu to say 'normal' rather than 'plain'. Although I must confess a preference for 'plain'.
Blast! I *knew* I'd seen something somewhere. My apologies - I should have checked under the approved posts. Well, at least that means I've not gone mad, thinking I'd imagined seeing posts.
OK, I'm going to look at all the magic-emphasis-number-users and make a changeset. If someone else does the same (or double-checks my work) then hopefully we can safely get rid of those magic-emphasis-number- users.
frank
but I approved a changeset that fixed all the sender of plain to be substituted by normal. So we do not need to have plain and normal. I do not see the point.
What should be fixed is that some places use number such as 1 2 3 instead of textEmphasis look for the sender of *emphasis:
stef
On 24 févr. 04, at 12:24, frank.shearar@rnid.org.uk wrote:
I looked for replies or fixes for this bug, but couldn't find any on BFAV. The bug's still present in my 5707 image so please just ignore this if the bug's already been fixed.
The attached changeset provides a simple fix. It adds TextEmphasis>>plain which just returns self normal.
It might be better to change the context menu to say 'normal' rather than 'plain'. Although I must confess a preference for 'plain'.
Blast! I *knew* I'd seen something somewhere. My apologies - I should have checked under the approved posts. Well, at least that means I've not gone mad, thinking I'd imagined seeing posts.
Welcome to hallucinations. I got the same :)
OK, I'm going to look at all the magic-emphasis-number-users and make a changeset. If someone else does the same (or double-checks my work) then hopefully we can safely get rid of those magic-emphasis-number- users.
ok I will have a look. Apparently from what I understood if you look into textEmphasis you will see that there are numer there too. so it should be possible to map 1 to TextEmphasis normal May be somebody knows better than I.
frank
squeak-dev@lists.squeakfoundation.org
-
ducasse -
Frank Shearar -
frank.shearar＠rnid.org.uk
-
Matej Kosik