On 11 Nov 2012, at 19:03, Quincey Morris
wrote:
> On Nov 11, 2012, at 04:09 , Luc Van Bogaert wrote:
>
>> However, when my application is not active when the file is dropped, the
>> message to the windowcontroller is never sent.
>>
>> Here's the relevant line of code in performDragOperation
My detail view is implemented using a UITableView. I want a nav bar at the top
of the detail view, to mimic the iPhone (which is provided by the nav
controller), and to provide a heading for the detail below.
Storyboard table views insist, rather restrictively, that the top-level view in
a UITa
Hmm. I guess I can just add an unnecessary UINavBarController. Feels wasteful,
but it'll do.
On Nov 12, 2012, at 1:58 , Rick Mann wrote:
> My detail view is implemented using a UITableView. I want a nav bar at the
> top of the detail view, to mimic the iPhone (which is provided by the nav
> c
Well, I spoke too soon. The UINavController solves the nav bar issue, but I
have another, custom, view, that I want to stick above my table view.
On Nov 12, 2012, at 2:01 , Rick Mann wrote:
> Hmm. I guess I can just add an unnecessary UINavBarController. Feels
> wasteful, but it'll do.
>
> On
I have a property:
@property (readonly) NSDictionary *someDictionary;
This property should be computed on demand, and should be accessible by several
threads.
My current implementation is:
- (NSDictionary *)someDictionary;
{
static NSDictionary *someDictionary;
st
Hi Hunter,
I am very interested in what bugs they fixed. Could you please share more
about it , e.g. an official bug fix report ?
Thanks
Bob
> The API changes came in iOS 5 but in iOS 6 they fixed enough bugs to make it
> work right. :-)
> On Nov 11, 2012, at 4:50 PM, Rick Mann wrote:
Looking at the docs, dispatch_once takes care of the synchronization for you:
https://developer.apple.com/library/mac/ipad/#documentation/Performance/Reference/GCD_libdispatch_Ref/Reference/reference.html
It should therefore be thread safe to use without any additional
synchronization code.
Se
On 12 Nov 2012, at 12:56, "Gerriet M. Denkmann" wrote:
> I have a property:
>
> @property (readonly) NSDictionary *someDictionary;
>
> This property should be computed on demand, and should be accessible by
> several threads.
>
> My current implementation is:
>
> - (NSDictionary
> This is completely the wrong way to implement a property. The static
> variable will be shared between all instances. Here's how you should be
> doing a lazy loaded var:
>
> @implementation MyClass
> {
>NSDictionary *_someDictionary
> }
>
> - (NSDictionary *)someDictionary
> {
>stat
On 12 Nov 2012, at 13:39, Marco Tabini wrote:
>> This is completely the wrong way to implement a property. The static
>> variable will be shared between all instances. Here's how you should be
>> doing a lazy loaded var:
>>
>> @implementation MyClass
>> {
>> NSDictionary *_someDictionary
This summs it up really nicely:
http://wbyoung.tumblr.com/post/27851725562/core-data-growing-pains
Links to radar bug reports are within the blog post.
The conclusion it is not usable does not hold under iOS6, since nested contexts
work quite wonderfully there, but it shows problems under iOS5.
You can use dispatch_sync. The blog post of oliver dobnigg (cocoanetics) summs
that up quite nicely:
http://www.cocoanetics.com/2012/02/threadsafe-lazy-property-initialization/
Cheers, Jörg
On Nov 12, 2012, at 2:44 PM, Tom Davie wrote:
>
> On 12 Nov 2012, at 13:39, Marco Tabini wrote:
>
>>>
On 12 Nov 2012, at 14:18, Joerg Simon wrote:
> You can use dispatch_sync. The blog post of oliver dobnigg (cocoanetics)
> summs that up quite nicely:
> http://www.cocoanetics.com/2012/02/threadsafe-lazy-property-initialization/
Or you can use dispatch_once, but make sure the once token is an i
As you can read in the blog too, the developer documentation of dispatch_once
states:
"The predicate must point to a variable stored in global or static scope. The
result of using a predicate with automatic or dynamic storage is undefined."
so, no, you can not. Actually it works most of the tim
In an earlier message, Quincey Morris recommended the use of a (presumably
AppKit) method named alertImageDragInDesignWithURL:. For the life of me, I
can't find that symbol in any documentation, nor in Xcode's Open Quickly…, nor
in a web search (turns up only his message, near as I can tell).
I
On 12 Nov 2012, at 3:58 AM, Rick Mann wrote:
> Storyboard table views insist, rather restrictively, that the top-level view
> in a UITableViewController be a table view. I'd really rather it be a regular
> view, and put the table view down inside the hierarchy. There's no good
> reason this ca
On Nov 12, 2012, at 8:41 AM, Joerg Simon wrote:
> On Nov 12, 2012, at 3:33 PM, Tom Davie wrote:
>
>> On 12 Nov 2012, at 14:18, Joerg Simon wrote:
>>
>>> You can use dispatch_sync. The blog post of oliver dobnigg (cocoanetics)
>>> summs that up quite nicely:
>>> http://www.cocoanetics.com/2012
Hello,
I noticed that iOS 5.x. has very strange problems in rotation especially in
"launching time".
While an app is being launched, it presents a logo image inside of a
UIImageView and presents a main GUI screen.
It's always on landscape mode.
What is weird with iOS 5 is that it works as intend
I'm debugging a crash in a large project which evidence indicates is caused by
a retain/release imbalance. The project is written with manual retain/release,
not ARC.
The project is built in Xcode 4.5.2, and when I 'Analyze', I get no warnings
pertaining to memory management. So the problem m
On 12 Nov 2012, at 17:19, Jerry Krinock wrote:
> I'm debugging a crash in a large project which evidence indicates is caused
> by a retain/release imbalance. The project is written with manual
> retain/release, not ARC.
>
> The project is built in Xcode 4.5.2, and when I 'Analyze', I get no
It has been awhile since I last did a conversion, but I do remember that when I
Analyzed my project it didn't raise any issues, but when I tried to convert to
ARC there were a few places where these issues were raised that I needed to
fix. Also, converting to ARC might actually move the retain/r
On Nov 12, 2012, at 07:17 , Fritz Anderson wrote:
> In an earlier message, Quincey Morris recommended the use of a (presumably
> AppKit) method named alertImageDragInDesignWithURL:. For the life of me, I
> can't find that symbol in any documentation, nor in Xcode's Open Quickly…,
> nor in a we
On Nov 12, 2012, at 9:19 AM, Jerry Krinock wrote:
> The project is built in Xcode 4.5.2, and when I 'Analyze', I get no warnings
> pertaining to memory management. So the problem must be some edge case which
> is not caught by 'Analyze’.
The analyzer definitely cannot detect all refcountin
On Nov 12, 2012, at 09:19 , Jerry Krinock wrote:
> I'm debugging a crash in a large project which evidence indicates is caused
> by a retain/release imbalance. The project is written with manual
> retain/release, not ARC.
>
> The project is built in Xcode 4.5.2, and when I 'Analyze', I get no
Thanks for the replies; very informative.
I followed Jens advice, got lucky, and fixed the problem manually. It turned
out to be an extraneous [self release] that should have been balanced by a
[self retain] in another method. I can understand how static analysis wouldn't
know what to make of
On Nov 12, 2012, at 8:36 AM, Ken Thomases wrote:
> Far be it from me to discourage people from paying attention to the docs, but
> I'm pretty sure that the docs are excessively restrictive in this case.
>
> From working with similar constructs in other APIs, I believe the actual
> requirements
On Nov 12, 2012, at 7:30 , Fritz Anderson wrote:
> The whole point of a UITableViewController is to have a controller that
> autonomously instantiates a table view as its root view. Interface Builder
> isn't making an arbitrary choice; the controller, not IB, creates the view.
Actually, I dis
I finally suceeded in doing what I needed to do, although it's not ideal.
It's possible to separate UITableViewController's view from its tableView. I
subclassed UITableViewController, and in -viewDidLoad I:
- Remember the current self.tableView in an ivar
- Create a UIView match
28 matches
Mail list logo
