On Aug 16, 2009, at 3:02 PM, Graham Cox wrote:
On 17/08/2009, at 1:47 AM, Squ Aire wrote:
Key-value pairs in the userInfo dictionaries are "marked as garbage"
as the app is running and depending on various factors.
Don't "mark as garbage" - delete them. Problem solved. If you need
them to s
On Aug 14, 2009, at 3:02 PM, Brad Gibbs wrote:
Actually, I wouldn't mind sending the relevant portion of the
persistent store over the network. The database is an in-house app
that many people will need to be able to work in simultaneously.
We'll use that database to create products and package
On Jul 4, 2009, at 9:10 PM, mmalc wrote:
If you manipulate an instance variable anywhere other than in an
initialiser or a dealloc method, you should use a suitable accessor
method.
On Jul 5, 2009, at 6:53 AM, mmalc wrote:
On Jul 4, 2009, at 9:40 PM, WT wrote:
[...]
There is plenty of Ap
On May 31, 2009, at 6:15 AM, erg_consult...@yahoo.com wrote:
Ok so more specifically I should have asked:
How do I get the NSSplitView to restore the divider position when my
app relaunches the next time?
I set the autosave name but when I drag the splitter, then quit and
relaunch, it's s
On May 31, 2009, at 12:10 AM, cocoa-dev-requ...@lists.apple.com wrote:
What does setAutosaveName actually do? I assume it saves the
position of the splitview to user defaults?
Did you read the fine manual? It's fairly plain:
"Sets the name under which receiver’s divider position is
automat
On May 7, 2009, at 2:21 AM, Graham Cox wrote:
A. each observable object class exports a list of properties that it
thinks may be of interest to an observer. This is just an array of
strings (property names) returned by a class method.
B. A utility method iterates over that list and registers a
On May 4, 2009, at 11:07 PM, johnmadst...@yahoo.it wrote:
I am confused.
Perhaps, but not nearly so much as your developer friend.
I was discussing with a developer about my desire to translate our C++
code (really simple and few methods and classes) to Objective-C, for a
Cocoa/Cocoa Touch
On Aug 31, 2008, at 3:13 AM, "Mr. Gecko" <[EMAIL PROTECTED]> wrote:
Hello I am making a program that does a really hard calculation and it
seems to crash after 60 Minutes. I don't really know why it does, I am
guessing it is because I am using a for loop that takes awhile to run
(an estaminet of
On Aug 30, 2008, at 12:30 AM, [EMAIL PROTECTED] wrote:
A program I have developed will not run on a PPC machine (G5
iMac) using OS 10.4.11. It was developed on Xcode 3.0 on an Intel
machine running OS 10.5.4. Initially the projects "Cross_Develop
Using Target SDK" was set to "Current Mac
On Aug 27, 2008, at 2:43 PM, Negm-Awad Amin and mmalc crawford argued:
You can subclass NSManagedObject and add properties using
@property and @dynamic, which means, that the accessors will be
generated dynamically at run-time. (Without @dynamic you will get
a compiler warning: incomplete imple
On Aug 14, 2008, at 8:36 PM, Markus Spoettl wrote:
When the user changes the preference, the view should update its value
so it uses the right units. There is no change to the underlying data,
so there's no change notification that would force the binding to
refresh the view.
So how can I manua
On Friday, July 25, 2008, at 01:43PM, Wesley Smith wrote:
>I have a question regarding memory ownership and NSMenus. Let's say I
>have an application with a nib file containing the usual menu items
>like File, Edit, Window etc. If, during the execution of my app, I
>swap out the Window menu with
On Jul 8, 2008, at 3:02 PM, [EMAIL PROTECTED] wrote:
Okay, got this message late though it looks like another had responded
to it already. Given that I need to override -keyDown: (or -
performKeyEquivalent:) in applicable first responders anyway, and it
doesn't really read well to have -forwardD
eason for putting the code above in a custom window controller
is that ideally, your document class shouldn't be in the business of
defining what the window should look like. The window controller is a
better place for that.
cheers,
Caleb Strockbine
___
array). I'm sure that there are ways that the docs could
be improved, but IMO, adding "don't forget to retain the returned
object" to the description for every method in every class in Cocoa that
returns an object would not be an improvement.
regards,
Caleb Strockbine
__
15 matches
Mail list logo
