Just a thought, I haven't tried it, but the Core Foundation code is
pure C, so you could send the NSString as a CFString, which is "toll-
free bridged", which should mean you don't even have to make a cast
(though, again, I haven't worked with this), but basically, you should
be able to crea
I still don't understand why the filters worked as expected when I
typed in the full string of one of the relationship's path's values,
but it doesn't worry me too much, since it's working now.
Dustin
KC9MEL
On Aug 8, 2008, at 6:11 PM, Dustin Robert Kick w
This can also be done with an NSFormatter. I've only worked through
one example, long enough ago that I can't give helpful details, but
you should be able to find an example on how to do something similar
to what you're trying to do. I believe the example I looked at was
using an NSForma
I have a program I'm developing where there will be one list, shown in
an NSTableView that has source objects, and a second list that
contains counted reference objects from the first list, also shown in
an NSTableView, and you add objects by selecting in the first list,
and clicking a butt
I have a program set up with core data, and I have a list of
predicates to filter the data shown, which work only if you type in
the entire string value of the data item being used to filter, though
I'm using "somePath contains[cd] $value" for the binding, where
somePath are various paths I
yes, indeed, that does seem to be the simplest solution, thanks.
Dustin
KC9MEL
On Aug 5, 2008, at 8:14 AM, Hamish Allan wrote:
On Mon, Aug 4, 2008 at 6:32 PM, Dustin Robert Kick <[EMAIL PROTECTED]
> wrote:
This seems like it would be common enough, to me, that it woul
This seems like it would be common enough, to me, that it would have
bindings for it. I can't find anything, and am thinking I will write
an NSValueTransformer to do this (also thought there might be a value
transformer for this, but no). Am I missing something? I thought
that there shou
Why not have the error messages simply be error messages, and leave
out the "clever" which I think is always a bad idea, anyway, in almost
any domain? Have it report an error that has a number indicating a
possible hackintosh, and double check if it is a hackintosh issue, or
a bug in your
