On Dec 10, 2013, at 1:07 PM, Pax <45rpmli...@googlemail.com> wrote:
> Ah! Exactly right. It is nil - but surely I shouldn't have to initialise
> it? I never have in the past - I built the UI with IB, and I was under the
> impression that that would handle all the initialisation for me.
The
Ah! Exactly right. It is nil - but surely I shouldn't have to initialise it?
I never have in the past - I built the UI with IB, and I was under the
impression that that would handle all the initialisation for me.
Given that I do have to initialise it, I'm guessing that it won't be as simple
Check for nil — in the set-the-state code add an assertion that
_onOffSwitch!=nil, and in -setActive: add an assertion that sender!=nil. That
may help track things down.
(Basically, any time I see a weird bug like “I change a property of ___ but it
doesn’t do anything” or “a property of ___ is
Thank you Kyle.
I'm taking a look at the layout. I have a question.
I don't need to auto-align the NSView. I need to let the user enter origin
and size of the view (excluding the shadow and frame) and get the view on
those coordinates and size.
Let's say I learn how to configure the layout with e.
Another weird one (or another paper bag error from me!)
I'm writing a pref pane and, when it loads, it checks to see if the application
that it provides the settings for is running or not. If the application is
running then it sets an NSButton to On, and if it isn't then it sets the button
to
On 10 Dec 2013, at 1:41 PM, Fritz Anderson wrote:
> Using the controls at the bottom-right of the Storyboard canvas, set the
> idiom to iOS 7. Open the Assistant editor and choose Preview. See what
> happens as you fiddle around with orientation and screen size, again with
> those controls at
On 10 Dec 2013, at 8:58 AM, Alex Zavatone wrote:
> I've just run across a nasty behaviour where with AutoLayout on iOS 7,
> sometimes a view will not appear at all after a segue.
>
> The scary thing is that this is intermittent, and will either happen all the
> time for a build or never for a
On Dec 10, 2013, at 11:16 AM, Robert Vojta wrote:
> When I’m testing it, it starts upload almost immediately, I see it in logs
> and then it suddenly stops after 160kB of data sent and is stalled ...
Is it possible this is a server-side issue? What exactly are you uploading it
to? Have you lo
On Dec 10, 2013, at 12:43 PM, Kyle Sluder wrote:
> On Dec 10, 2013, at 10:38 AM, Charles Srstka wrote:
>>
>> How about sandboxed applications? Their preference files are opaque to
>> NSUserDefaults, and only sometimes visible to /usr/bin/defaults. How should
>> one delete a corrupted plist fi
Hi all,
I’ve got issues with NSURLSessionUploadTask and maybe I missed something. My
NSURLSession has background configuration, cellular data allowed and
discretionary property set to NO. The configuration is …
NSURLSessionConfiguration *configuration = [NSURLSessionConfiguration
backgroundS
On 10 Dec 2013, at 6:08 pm, Kyle Sluder wrote:
> Bingo. You are now caught up with the original post in this thread.
>
> The plist files are and always have been an implementation detail. The only
> supported interface to preferences has always been through
> CFPreferences/NSUserDefaults, whe
On Dec 10, 2013, at 10:38 AM, Charles Srstka wrote:
>
> How about sandboxed applications? Their preference files are opaque to
> NSUserDefaults, and only sometimes visible to /usr/bin/defaults. How should
> one delete a corrupted plist file in a sandbox?
Not sure what you mean by "opaque." If
On Dec 10, 2013, at 10:25 AM, Seth Willits wrote:
>
> The idea is that by using it you push drawing commands into the ether which
> may end up being drawn on the GPU via QE (I don't know that anyone said that,
> but it's something that occurred to me, I'm just not sure on how that's done
> int
On Dec 10, 2013, at 11:08 AM, Kyle Sluder wrote:
>> On Dec 10, 2013, at 7:46 AM, Jakob Egger wrote:
>
>>
>> Or does OS X Mavericks recreate deleted preference files in some cases?
>
> Bingo. You are now caught up with the original post in this thread.
>
> The plist files are and always have
On Dec 10, 2013, at 1:32 AM, Graham Cox wrote:
>> Which is another reason to seriously consider CATiledLayer
>
> I”ll consider it, and revisit it…
>
> But my situation is that I need to draw VECTOR objects up to 25,000% zoom
> with no pixelization.
You're given a CGContext to draw into; What'
On Dec 10, 2013, at 2:47 AM, Kevin Meaney wrote:
> I'm probably teaching my grandmother to suck eggs by suggesting this. Have
> you looked at using CGLayers?
They're extremely heavy. You definitely don't want them around if performance
is a consideration.
--
Seth Willits
_
> On Dec 10, 2013, at 7:46 AM, Jakob Egger wrote:
>
> Or does OS X Mavericks recreate deleted preference files in some cases?
Bingo. You are now caught up with the original post in this thread.
The plist files are and always have been an implementation detail. The only
supported interface to
On 10 Dec 2013, at 04:14 pm, Jens Alfke wrote:
>
> On Dec 10, 2013, at 2:24 AM, Jakob Egger wrote:
>
>> Maybe I am missing something really obvious
>
> Yup, you are. You didn’t read back to the beginning of this thread, which
> started with the observation that the OS sometimes caches prefs
On Dec 10, 2013, at 6:04 AM, Appa Rao Mulpuri wrote:
> Imagine we have release cycle for every two weeks, but need to build a
> feature that's going to take three months to complete. How do you use
> Continuous Integration to keep everyone working on the mainline without
> revealing a half-imple
On Dec 10, 2013, at 2:24 AM, Jakob Egger wrote:
> Maybe I am missing something really obvious
Yup, you are. You didn’t read back to the beginning of this thread, which
started with the observation that the OS sometimes caches prefs even after the
plist file is deleted, making this technique n
I've just run across a nasty behaviour where with AutoLayout on iOS 7,
sometimes a view will not appear at all after a segue.
The scary thing is that this is intermittent, and will either happen all the
time for a build or never for a build.
Turning off AutoLayout appears to fix the issue, but
On 10 Dec 2013, at 15:04, Appa Rao Mulpuri wrote:
> We have a configuration file that defines a bunch of toggles for various
> features you have pending. The running application then uses these toggles
> in order to decide whether or not to show the new feature.
The solution is to do those othe
I believe google has something called google tag manager that could be useful.
You can remotely enable or disable features in your app.
I do believe the scenario you're describing is the right time for a remote
branch that could be rolled into master when the feature is completed.
Otherwise, s
Imagine we have release cycle for every two weeks, but need to build a
feature that's going to take three months to complete. How do you use
Continuous Integration to keep everyone working on the mainline without
revealing a half-implemented feature on your releases?
To solve the issue:
We have
On 10 Dec 2013, at 14:31, Appa Rao Mulpuri wrote:
> Do we have toggle framework in Cocoa? I searched in the internet and found
> http://www.togglz.org/, which is written in Java. I am curious, we have
> equivalent in Cocoa as well.
What does it do?
-- Uli Kusterer
"The Witnesses of TeachText
Hi List,
Do we have toggle framework in Cocoa? I searched in the internet and found
http://www.togglz.org/, which is written in Java. I am curious, we have
equivalent in Cocoa as well.
- Apparao M
This email and any attachments are confidential, and may be legally privileged
and protected by
I'm probably teaching my grandmother to suck eggs by suggesting this. Have you
looked at using CGLayers?
Kevin
On 10 Dec 2013, at 10:08, Graham Cox wrote:
>
> On 10 Dec 2013, at 10:52 am, Mike Abdullah wrote:
>
>> Another option to consider is using CAShapeLayer to render individual
>> obj
On 27 Nov 2013, at 08:27 pm, Graham Cox wrote:
> Great. For me. For users in the field, the command line is the badlands, and
> we can’t expect many users to be comfortable doing that. Trashing a file is
> at least something they can understand, even if sometimes even that can be an
> ordeal
On 10 Dec 2013, at 10:52 am, Mike Abdullah wrote:
> Another option to consider is using CAShapeLayer to render individual objects
> where reasonable. This should allow Core Animation to efficiently render such
> vectors without a dedicated backing store.
CAShapeLayers really don’t scale much
On 10 Dec 2013, at 09:32, Graham Cox wrote:
>
> On 9 Dec 2013, at 11:12 pm, Kyle Sluder wrote:
>
>> Which is another reason to seriously consider CATiledLayer
>
>
> I”ll consider it, and revisit it…
>
> But my situation is that I need to draw VECTOR objects up to 25,000% zoom
> with no pi
On 10 Dec 2013, at 12:39 am, Seth Willits wrote:
> There’s NSView’s bitmapImageRepForCachingDisplayInRect: and you can grab a
> colorspace from the rep. I would certainly imagine that has the ideal space
> and you can confirm it’s one or another. You can use that method to create
> your presu
On 9 Dec 2013, at 11:12 pm, Kyle Sluder wrote:
> Which is another reason to seriously consider CATiledLayer
I”ll consider it, and revisit it…
But my situation is that I need to draw VECTOR objects up to 25,000% zoom with
no pixelization. That means the CATileLayer needs to remain firmly “stu
32 matches
Mail list logo
