I see now a change on Pharo 1.3 in the way for configure a text field for
accept only numeric values. Before I configure a text field of that way:
aNumericTextField converter: ((ObjectTransformedStringConverter
forClass:
Integer)
transformBlock: [:s | s select:
Hi scott
could you enter a bug tracking entry for each of these items that we
should fix?
Thanks for reporting that.
Stef
On Apr 18, 2009, at 4:15 AM, Scott Gibson wrote:
I have noticed with the newer releases (pharo0.1-10277dev09.04.2 and
pharo0.1-10279dev09.04.3) there, which seemed to
These are actual issues
Thanks for spotting them.
Probably these changes got reverted when the changes of eliot got
merged back.
argh!
Stef
On Apr 18, 2009, at 4:15 AM, Scott Gibson wrote:
I have noticed with the newer releases (pharo0.1-10277dev09.04.2 and
pharo0.1-10279dev09.04.3) there,
I have noticed with the newer releases (pharo0.1-10277dev09.04.2 and
pharo0.1-10279dev09.04.3) there, which seemed to me, to be fixes/
improvements that were lost from the earlier (Pharo0.1Core-10268cl and
pharo0.1-10268dev09.04.1) releases. These following occur for both
the Mac and