Hello,
I am using Xcode 6.1.1 on OS X Yosemite and have exported an archive as a Mac
Installer Package using a Developer ID to sign it. The installer is created
successfully, and when run, the installer executes the installation
successfully. But when I attempt to launch the app, it crashes
On Feb 6, 2015, at 11:34:35, Kyle Sluder k...@ksluder.com wrote:
Dealloc is too late for a lot of this stuff. I try to keep -dealloc as
pure as possible; that is, -dealloc should only be concerned with memory
management.
Removing observers, unbinding, unregistering notifications, and timer
Alex,
Don’t know….in my case, this was OS X
Sandy
On Feb 11, 2015, at 8:25 PM, Alex Zavatone z...@mac.com wrote:
Any idea if this only affects OS X or does it also affect iOS?
Sent from my iPad. Please pardon typos.
On Feb 11, 2015, at 12:55 PM, Sandy McGuffog mcguff...@gmail.com
Brad,
Yes, Xcode 6 breaks what used to be valid signing workflows under previous
versions. Unfortunately, Apple’s documentation hasn’t caught up, and most of
DTS is clueless on this subject. It took me literally months to get a useful
answer. This BTW is not a bug, it is apparently as a result
On Feb 11, 2015, at 13:06:20, Steve Mills sjmi...@mac.com wrote:
This also sparked my understanding of the other binding attributes, like
Multiple Values Placeholder and such, resulting in me not needing my special
EnableOnlyFor1ItemXformer value transformer on the array controller
Any idea if this only affects OS X or does it also affect iOS?
Sent from my iPad. Please pardon typos.
On Feb 11, 2015, at 12:55 PM, Sandy McGuffog mcguff...@gmail.com wrote:
Brad,
Yes, Xcode 6 breaks what used to be valid signing workflows under previous
versions. Unfortunately, Apple’s
Thanks for the mental prodding, guys. I did some sleuthing by added an observer
for the array controller's selectedObjects.@count in code so I could watch it
as well as the comboStringValue property. When the selection changed and the
combobox was empty, I noticed the comboStringValue property
On Feb 11, 2015, at 1:25 PM, Steve Mills sjmi...@mac.com wrote:
On Feb 11, 2015, at 13:06:20, Steve Mills sjmi...@mac.com wrote:
This also sparked my understanding of the other binding attributes, like
Multiple Values Placeholder and such, resulting in me not needing my special
On Feb 11, 2015, at 13:51:29, Ken Thomases k...@codeweavers.com wrote:
The selectedObjects property never returns those placeholders. Only the
selection property does that. However, that wouldn't support @count, I don't
think.
@count appears to work on selection when I tested it, FYI.
I have a Core Data in-memory store. There is a managed object which uses KVO on
a to-many relationship property of itself.
When an object at the other end of the relationship is deleted using
[managedObjectContext deleteObject:object] the KVO change notification is not
sent right away.
What
On 12 Feb 2015, at 07:27, Richard Charles rcharles...@gmail.com wrote:
I have a Core Data in-memory store. There is a managed object which uses KVO
on a to-many relationship property of itself.
When an object at the other end of the relationship is deleted using
[managedObjectContext
On Feb 11, 2015, at 4:51 PM, Roland King r...@rols.org wrote:
committing the core data changes removes them from all the relationships and
fires KVO changes. see propagatesDeletesAtEndOfEvent: and
commitPendingChanges. In AppKit usually deletes are propagated once around
the event loop,
On 12 Feb 2015, at 08:27, Richard Charles rcharles...@gmail.com wrote:
On Feb 11, 2015, at 4:51 PM, Roland King r...@rols.org wrote:
committing the core data changes removes them from all the relationships and
fires KVO changes. see propagatesDeletesAtEndOfEvent: and
All,
Thank you to those who replied — I really appreciate it. The problem is solved,
so I thought I’d pass it on for anyone else that runs into this issue.
I opened a tech support incident with DTS, and received a fairly prompt
response from Apple DTS, who directed me to the following
Control-clicking the button in .xib does show the outlet panel but it does not
list an IBAction, so it cannot connect to the IBAction entered into the
MyView.h and .m files. Also, control-dragging from the button to MyView (in
.xib, not in editor) sets up the position constraints.
Hi Andy,
NSLog(@isAutomaticTextReplacementEnabled %d, [NSSpellChecker
isAutomaticTextReplacementEnabled]);
NSLog(@isAutomaticSpellingCorrectionEnabled %d, [NSSpellChecker
isAutomaticSpellingCorrectionEnabled]);
but no corresponding set methods!?
Note that you're messaging the
On 12 Feb 2015, at 13:36, N!K pu56ucl...@alumni.purdue.edu wrote:
Control-clicking the button in .xib does show the outlet panel but it does
not list an IBAction, so it cannot connect to the IBAction entered into the
MyView.h and .m files. Also, control-dragging from the button to MyView
On Feb 11, 2015, at 5:36 PM, Roland King r...@rols.org wrote:
processPendingChanges:, it’s on NSManagedObjectContext
That’s what I was looking for.
Thanks for your help.
Richard Charles
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
18 matches
Mail list logo