[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Patches for NSCell.m, NSActionCell.m, NSNumberFormatter.m
From: |
Dirk Lattermann |
Subject: |
Patches for NSCell.m, NSActionCell.m, NSNumberFormatter.m |
Date: |
Mon, 26 May 2003 22:10:46 +0200 |
User-agent: |
Mutt/1.4i |
Hello,
EOInterface's EOControlAssociation works by setting the object value
of its control. When binding it to an NSTextField, I noticed that
the text field doesn't show the value set by the association.
The other way around, after typing text into an NSTextField, one
cannot read its value out via objectValue as I now think one should
be able to (see my recent post on NSTextField one or two weeks ago).
The first case is obviously caused by a missing setObjectValue: in
NSActionCell (see attached patch).
The second case seems to be repaired by my patch attempt on NSCell.m,
but I'm not sure if it's right. Maybe _contents and _objectValue
mustn't point to the same string, i.e., one should be copied. Or maybe
the string value/object value mechanism isn't meant to be like I assume?
My patch on NSNumberFormatter.m is a quick, easy and dirty way to
provide at least a conversion from string to number for simple numbers
(e.g. integers) without any provided format. I think it's better than
no conversion at all, maybe an NSLog should be added that no real
converter is in place, use at own risk, etc. I couldn't find out if
the returned anObject should be retained or not, so that must maybe
added.
Please, could someone look over these small patches and apply them
if appropriate?
Thanks,
Dirk Lattermann
NSActionCell.m.patch
Description: Text document
NSCell.m.patch
Description: Text document
NSNumberFormatter.m.patch
Description: Text document
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Patches for NSCell.m, NSActionCell.m, NSNumberFormatter.m,
Dirk Lattermann <=