Dear All,
To be user-friendly my app would need to use per-user preferences and global
preferences (i.e. that applies to all users). The former I can manage. The
later… well, short of coding a helper tool just for dealing with preferences
storage, I have no idea on how to proceed. I would rathe
Thank you very much for your reply. It was really helpful.
Jean
> There is an other way to track the current user: using the
> SystemConfiguration framework notification:
>
> http://developer.apple.com/library/mac/#qa/qa1133/_index.html
>
> -- Jean-Daniel
>
>
>
>
___
I want to switch to blocks instead of delegates for small callbacks,
e.g. operationDidFinish or animationDidFinish, but there is a question
I cannot understand.
There is the typical scenario when I need to run an operation (usually
in another thread) and while it is running, I should ignore new
re
> However, when I use completion blocks instead of delegates, things get
> somewhat vague.
>
> Is it still necessary to store the current operation in a property, or
> does each operation get its own independent copy of the completion
> block, together with its current context? What happens if I
Thanks, Roland.
I can see you are comparing the member variable currentOperation of
the caller's class and a locally declared variable
currentOperationAtQueueTime. Good idea. Obviously, the block retains
"self" of the caller object and all local variables referenced from
within the block. So when
This helped enormously. I was not familiar with the
resursiveDescription method. Using it, I could see that my view-of-interests
parent UIImageView had the userInteraction property set to NO. Changed that,
and now I'm getting my events.
Thanks much!
On Mar 15, 2013, at 11:10 AM, Da
On Mar 16, 2013, at 4:14 AM, Jean Suisse wrote:
> To be user-friendly my app would need to use per-user preferences and global
> preferences (i.e. that applies to all users). The former I can manage. The
> later… well, short of coding a helper tool just for dealing with preferences
> storage, I
I've got a paging UIScrollView with two views/pages on it that scrolls
horizontally. We are playing with a few UI ideas and as part of that I'd like
to programmatically "bounce" the scroll view. The idea is that as you open the
app, we peek into the second page and then bounce it back to the fir
I'm working with ARC for the first time just now. I'm running into an issue
where ARC is releasing objects too soon and I am not sure the best way to fix
it. Under GC it works correctly, even in the same project if I turn off ARC and
turn GC back on.
I have an AppDelegate that will spawn any num
On 16 Mar 2013, at 06:16 PM, Chris Paveglio wrote:
> So, am I doing some fundamental window management wrong (not sure since old
> app worked OK and didn't seem to leak), or how do I do something so ARC
> doesn't dealloc window controllers at the end of the function that fires them
> off
If
UIScrollView has specific notes on how to use autolayout: the iOS 6.0
Release Notes have a good explanation on this page (search for "Auto
Layout support"):
http://developer.apple.com/library/ios/#releasenotes/General/RN-iOSSDK-6_0/
index.html
Are there similar notes on how to use autolayout with
Sure I totally understand that. My question is more of "what is the most
elegant way to do it". Add them to an array?
- Original Message -
From: iain
To: Chris Paveglio
Cc: Cocoa Dev List
Sent: Saturday, March 16, 2013 2:35 PM
Subject: Re: ARC Release too soon
On 16 Mar 2013, at 06
I'd think adding the WindowController to a @property (strong, nonatomic)
NSArray *array; would keep those objects alive. Most often, I would simply add
each WindowController (or in my case, ViewController) one-at-a-time in the .h.
I simply feel it's clearer to see.
@property (strong, nonatomic)
On Mar 16, 2013, at 12:46 PM, Chuck Soper wrote:
> Are there similar notes on how to use autolayout with NSScrollView? Does
> anyone know the specific details on what Apple recommends? For example,
> are both mixed and pure autolayout approaches okay with NSScrollView? (The
> mixed or pure autola
On 3/16/13 3:05 PM, "Kyle Sluder" wrote:
>On Mar 16, 2013, at 12:46 PM, Chuck Soper wrote:
>
>> Are there similar notes on how to use autolayout with NSScrollView? Does
>> anyone know the specific details on what Apple recommends? For example,
>> are both mixed and pure autolayout approaches oka
Thanks to Kyle Sluder's recent "Re: guidelines for using autolayout with
NSScrollView?" post, I have a better understanding of what's involved in
getting auto layout to work with NSScrollView.
I thought I'd create a new thread because I'm not sure I need to take that
general approach for my specif
On 17 Mar 2013, at 12:38 AM, Chuck Soper
> Each subview has an "NSLayoutConstraint * widthConstraint;" ivar that
> holds the absolute width. Visually, it looks like this:
> @"H:[subview(==120)]"
>
>
> I also added some minimum width and height constraints that look like this:
> @"H:[subview(>
On Sat, Mar 16, 2013, at 06:37 PM, iain wrote:
>
>
> On 17 Mar 2013, at 12:38 AM, Chuck Soper
> > Each subview has an "NSLayoutConstraint * widthConstraint;" ivar that
> > holds the absolute width. Visually, it looks like this:
> > @"H:[subview(==120)]"
> >
> >
> > I also added some minimum w
On Sat, Mar 16, 2013, at 05:38 PM, Chuck Soper wrote:
> I thought I'd create a new thread because I'm not sure I need to take
> that
> general approach for my specific case. My user interface works fine. The
> problem is that my documentView is ambiguous, but I think I can ignore
> that fact for my
On 3/16/13 6:59 PM, "Kyle Sluder" wrote:
>On Sat, Mar 16, 2013, at 05:38 PM, Chuck Soper wrote:
>> I thought I'd create a new thread because I'm not sure I need to take
>> that
>> general approach for my specific case. My user interface works fine. The
>> problem is that my documentView is ambigu
On Mar 16, 2013, at 8:57 PM, Chuck Soper wrote:
>
> Is persistent layout ambiguity (for the documentView only) necessarily a
> problem? My UI works fine. I don't see how having the documentView
> ambiguous is causing a problem.
Yes, it's a problem. In my talk I reference a bug we had where, bec
If it's for windows where the number of them is under user control, then I
typically add them to a an array (which is a strongly retained property) then
you can either listen for window closing notifications and remove them, or if
the user may open the same window again, then you can check the a
22 matches
Mail list logo
