I have a very old app in the app store (last updated in pre-iPhone 5 days). One
of its bugs is that it crashes on first launch. I always assumed it was taking
too much time to process the large amount of data it now downloads, or used to
much memory in doing so. But looking into it, it's somethi
I'm writing a single-window utility application in Xcode 6.1.1 on OS X 10.10.2
using Swift 1.1. This code statement crashes:
let panel = NSOpenPanel()
For the first several days after I added this statement, it worked correctly --
the panel opened and I was able to select a file in the pan
Let's say I have a Mac app store app but for intermediate releases and/or
support of trial version I would like to also have version that is
distributed from my own site. So besides the app store build I would have
another build (distributed by me) that needs to know whether there is a
valid app st
On 19 Feb 2015, at 9:59 PM, Peters, Brandon wrote:
> I added a bridging header so that I could use the FMDB Objective-C code in
> Swift. However, the compiler still says it cannot recognize the datatype.
> Under Swift Compiler -> Code Generation I added the bridging header there. Is
> there so
My App has one window which is displayed. I want to display a sheet when a
button is clicked.
In the action for the button click I do:
ETAboutWindowController *windowController = [[ETAboutWindowController
alloc] initWithWindowNibName:@"ETAboutWindowController"];
[NSApp beginSheet:[windo
On Fri, Feb 20, 2015, at 12:54 PM, Raglan T. Tiger wrote:
> My App has one window which is displayed. I want to display a sheet when
> a button is clicked.
>
> In the action for the button click I do:
>
> ETAboutWindowController *windowController = [[ETAboutWindowController
> alloc] ini
We have a CoreData database on iOS that we want our users to be able to restore
in our OS X app from backups. It uses UIColor while our desktop app uses
NSColor for now. The correct method for us is to save our color info in a
non-platform specific way…but people have database backups where its
> On Feb 20, 2015, at 12:09 PM, Kyle Sluder wrote:
>
> Inspect the "Display At Launch" checkbox for the window in the nib.
Under Behavior , "Visible at Launch" is not selected.
-rags
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do
On Feb 20, 2015, at 13:19:11, Raglan T. Tiger wrote:
>
> Under Behavior , "Visible at Launch" is not selected.
Also ensure that the Title Bar attribute is turned on. This tripped me up for
hours as well. It totally goes against what should be logical. After all,
sheets don't appear with a titl
> On Feb 20, 2015, at 12:27 PM, Steve Mills wrote:
>
> Also ensure that the Title Bar attribute is turned on.
Under Appearance "Title Bar" and "Shadow" are selected.
-rags
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post ad
On Feb 20, 2015, at 12:35 PM, Raglan T. Tiger wrote:
>
>> On Feb 20, 2015, at 12:27 PM, Steve Mills wrote:
>>
>> Also ensure that the Title Bar attribute is turned on.
>
> Under Appearance "Title Bar" and "Shadow" are selected.
Does [NSApp mainWindow] return a non-nil value at the point the
On Feb 20, 2015, at 13:51:35, Keary Suska wrote:
>
> Does [NSApp mainWindow] return a non-nil value at the point the code is
> invoked?
Or is it pointing to the same window that you're trying to make a sheet?
--
Steve Mills
Drummer, Mac geek
___
C
> On Feb 20, 2015, at 12:51 PM, Keary Suska wrote:
>
> Does [NSApp mainWindow] return a non-nil value at the point the code is
> invoked?
> On Feb 20, 2015, at 12:57 PM, Steve Mills wrote:
>
> Or is it pointing to the same window that you're trying to make a sheet?
2015-02-20 13:17:57.666
On Feb 20, 2015, at 14:34:29, Raglan T. Tiger wrote:
>
> 2015-02-20 13:17:57.666 [5613:177188] aboutWindowController
>
> 2015-02-20 13:17:57.666 [5613:177188] aboutWindowController window 0x601e9500>
> 2015-02-20 13:17:57.666 [5613:177188] mainWindow window 0x601e9500>
>
> You can se
Oops, we lost the cocoa list for a message or two. Re-adding.
> On Feb 20, 2015, at 14:28:12, Shane Stanley
> wrote:
>
> On 20 Feb 2015, at 7:13 pm, Steve Mills wrote:
>>
>> But why isn't it already set up to use the correct format like every other
>> place where a date is formatted?
>>
>>
On Feb 20, 2015, at 1:34 PM, Raglan T. Tiger wrote:
> 2015-02-20 13:17:57.666 [5613:177188] aboutWindowController
>
> 2015-02-20 13:17:57.666 [5613:177188] aboutWindowController window 0x601e9500>
> 2015-02-20 13:17:57.666 [5613:177188] mainWindow window 0x601e9500>
>
> You can see
On Feb 20, 2015, at 2:34 PM, Raglan T. Tiger wrote:
> So, I added an outlet of the app window and get:
>
> 2015-02-20 13:28:21.563 [5792:181060] aboutWindowController
>
> 2015-02-20 13:28:21.563 [5792:181060] aboutWindowController window 0x6180001edb00>
> 2015-02-20 13:28:21.563 [5792:181060]
> On Feb 20, 2015, at 2:09 PM, Ken Thomases wrote:
>
> Are you sure the app window (m_window) is the window you think it is? Log
> its title and its "visible" property.
NSWindow *appWindow = [NSApp mainWindow];
ETAboutWindowController *aboutWindowController = [[ETAboutWindow
On Feb 20, 2015, at 11:15 , Alex Kac wrote:
>
> So with that in mind, has anyone tackled a conversion process of reading in
> UIColor data into NSColor via CoreData?
I suspect that *really* solving this is going to be impossible.
When you say “UIColor data”, do you mean the data resulting from
Would it be correct to not care about UIColor or NSColor, encode the data to be
stored in 64 bit NSData, store that and when accessed, decode it?
Sent from my iPad. Please pardon typos.
On Feb 20, 2015, at 2:15 PM, Alex Kac wrote:
> We have a CoreData database on iOS that we want our users to
That would only work it UIColor and NSColor would encode themselves in exactly
the same way. Any guess what, they aren’t.
Georg
On 20 Feb 2015, at 22:53, Alex Zavatone wrote:
> Would it be correct to not care about UIColor or NSColor, encode the data to
> be stored in 64 bit NSData, store tha
Since we’ll be changing future databases to store the data as our own “PIColor”
that can be made into an NSColor/UIColor, the issue isn’t all that important
for long/term/future - but simply backups made already from the last 5 years.
So if there is a way that we can get it working 9 times out o
22 matches
Mail list logo
