>> In using Core Data, I was under the impression that if I do this:
>>
>> [department addEmployeesObject:employee] // department now has 1 employee
>> [moc deleteObject:employee]
>>
>> Then department will end up with no employees, assuming that the inverse
>> relationship is set correctly.
>>
Hi,
under Mac OS 10.6, an NSLocale seems to contain the information whether a
currency symbol should be put before the amount or behind it, like in $100.00,
or 100,00€.
Sadly, I was not able to find a way to specify this using the NSLocale/CFLocale
APIs. Is this a private piece of information?
Hello Gideon,
in contrast to the warnings in Apple's documentation, using a custom subclass
of NSManagedObjectContext is fine and often necessary to enrich the context
information of your managed objects. We have successfully using this technique
for complex applications since the first version
Does anybody know how to get file promises working with the new pasteboard API
in Snow Leopard?
When the dragging session in started, I put the following item onto the
provided pasteboard:
NSPasteboardItem* item = [[NSPasteboardItem alloc] init];
[item setDataProvider:self forTypes:[NSAr
Am 21.08.2009 um 17:49 schrieb I. Savant:
On Aug 21, 2009, at 11:31 AM, Frank Illenberger wrote:
Yes, I am using an sqlite store, but I tried it with the other
store types and it did not work either. What would a working
predicate look like for other store types?
I didn't catch
"ANY (employees.salary < %@ AND employees.dateOfBirth > %@)"
But it doesn't. Does anybody know if there is a way to use the ANY
statement with more than one condition?
Are you using the sqlite store type? "ANY" can't be used in a
compound predicate (AND) with the sqlite store type.
Yes,
Hi there,
in the typical CoreData example, if I want to fetch all departments
whose employees have a salary higher than a specified value, I will
perform a fetch on the Department entity using a predicate with the
following format:
"ANY employees.salary < %@"
This is working fine.
Now I
I second Andreas. For most cases, the correct place to declare
instance variables should be the .m file as they are an
implementation detail and not part of the contract with the outside
world using the class. The feature of non-fragile instance
variables of the modern ABI should make this
And what prevent you to simply declare the ivar in the interface
instead of letting the compiler generating it ?
I second Andreas. For most cases, the correct place to declare
instance variables should be the .m file as they are an implementation
detail and not part of the contract with the
Lite stuff will convert this to the proper SQL.
Good luck!
-bd-
http://bill.dudney.net/roller/objc
On Oct 7, 2008, at 6:04 AM, Frank Illenberger wrote:
Hi Bill,
I tried using predicates for this but did not succeed.
What would a predicate look like which finds the object of an
entity with
So the SQL engine will do that work. (Anyway the SQL engine of
course has to read every value.)
-bd-
http://bill.dudney.net/roller/objc
On Oct 7, 2008, at 3:49 AM, Frank Illenberger wrote:
Hi everybody,
does anybody know if CoreData under Leopard offers a way to fetch
the object of
://developer.apple.com/documentation/Cocoa/Conceptual/Predicates/predicates.html#/
/apple_ref/doc/uid/TP40001798
Good luck!
-bd-
http://bill.dudney.net/roller/objc
On Oct 7, 2008, at 3:49 AM, Frank Illenberger wrote:
Hi everybody,
does anybody know if CoreData under Leopard offers a way to fetch
the object of
Hi everybody,
does anybody know if CoreData under Leopard offers a way to fetch the
object of an entity which the maximum of a certain property value, but
without having to fetch all objects into memory?
Cheers
Frank
___
Cocoa-dev mailing list
Am 11.09.2008 um 18:15 schrieb Bill Bumgarner:
On Sep 11, 2008, at 8:47 AM, Frank Illenberger wrote:
As I understand it, try/catch blocks should be very fast (zero
cost) in the 64 bit evironment. As I can't observe the generation
of any exceptions, there has to be some other reason fo
_NSAppKitLock
1.5%Unknown Library
-[NSView nextKeyView]
1.2%Unknown Library
-[NSView _primitiveSetNextKeyView:]
Am 11.09.2008 um 15:07 schrieb Matt Gough:
On 11 Sep 2008, at 14:49, Fr
Am 11.09.2008 um 14:04 schrieb Jean-Daniel Dupas:
Le 11 sept. 08 à 13:01, Frank Illenberger a écrit :
Hi there,
I migrated an existing cocoa application to run under x86_64 with
Xcode 3.1 / Mac OS 10.5.4. The app still runs fine under 32 bit
but when started in x86_64 mode, it runs
Hi there,
I migrated an existing cocoa application to run under x86_64 with
Xcode 3.1 / Mac OS 10.5.4. The app still runs fine under 32 bit but
when started in x86_64 mode, it runs about 3-4 times slower.
A shark profile reveals the following hot traces:
8.9%libgcc_s.1.dylib_U
Hi there,
I migrated an existing cocoa application to run under x86_64 with
Xcode 3.1 / Mac OS 10.5.4. The app still runs fine under 32 bit but
when started in x86_64 mode, it runs about 3-4 times slower.
A shark profile reveals the following hot traces:
8.9%libgcc_s.1.dylib_Unw
Hi there,
has anybody successfully used NSNumberFormatter's new setLenient:
feature that was introduced with 10.5 together with one of the common
number styles like currency or percent? As usual, I want the formatter
to show a currency or percent symbol when turning numbers into strings
b
19 matches
Mail list logo
