I read “Sent when the user starts up the application on the command line with
the -NSPrint option.” as part of the documentation for NSApplicationDelegate’s
-application:printFile: method. I tried that when testing my printing; I added
“-NSPrint” as one of my command line fragments in the Scheme
On Aug 24, 2014, at 9:07 AM, Motti Shneor wrote:
> My OS-X app is using ARC, is CoreData Document-Based (using the old
> NSPersistentDocument) and uses 10.9 SDK.
>
> Up until now, I did nothing on my behalf to support user Undo/Redo, still the
> application seemed to work fine. I was very imp
[Usual disclaimer about incomplete information.]
On Aug 22, 2014, at 11:25 PM, Peters, Brandon wrote:
> I am getting this error:
>
> EXC_BAD_INSTRUCTION (code=EXC_I386_INVOP, subcode 0x0)
>
> over this line of code:
>
> if self.contentView!.frame.size.width > photo.size.width {
>
Hi.
My OS-X app is using ARC, is CoreData Document-Based (using the old
NSPersistentDocument) and uses 10.9 SDK.
Up until now, I did nothing on my behalf to support user Undo/Redo, still the
application seemed to work fine. I was very impressed with Cocoa (this
millionth time).
However. In
On 24 Aug 2014, at 02:00, Holmberg Bertil wrote:
> The first part of this method shows how to get the glyph from any character
> Works fine with non-Latin characters such as Japanese too
Does it also work with aChar starting with the Japanese HIRAGANA LETTER ARCHAIC
YE (U+1B001) ?
Hint: chars[
Hi Ken, thanks for answering.
> From what perspective?
From the perspective of the API, i.e.
- after `close` returns, windowWillClose was already being called
- after calling `miniaturize`, windowDidMiniaturize was already being
called and isMiniaturized is guaranteed to return true.
etc.
From
On Aug 24, 2014, at 1:05 AM, Samuel Williams
wrote:
> I'm generating a NSAttributedString which looks like the following:
>
> function_name_1
> disassembled code output
> disassembled code output
> disassembled code output
> function_name_2
> disassembled code output
> disassembled code output
