On 23 Oct 2014, at 00:34, Beinan Li wrote:
> Oh! I did actually.
>
> The method I posted belongs to an ObjC object which is wrapped by a C++
> object.
> That C++ object is a singleton (static).
>
> How is this going to affect ARC and why it didn't down-right crash a week ago
> before I upgr
Thank you Kevin!
I didn't know this before. This might be it because I did at some point
change the dictionary creation from the old API-based syntax to literals.
Maybe I should move back to the API calls. I'll try that today.
Thanks,
Beinan
On Thu, Oct 23, 2014 at 5:18 AM, Kevin Meaney wrote:
Personally I'd try and not call any objective-c code from a C++ static object.
If it did look the appropriate solution then I'd make sure I was comfortable
with my knowledge of the objective-c runtime and the order in which things are
called before main is called.
Kevin
On 23 Oct 2014, at 13:0
I just started seeing this in Xcode 5.1.1 the post few days under iOS 7.
In the tableView:cellForRowAtIndexPath, you can log the indexPath and the
results are not nil, but attempting to display [indexPath row] or section
results in nil.
My only clue here is that this VC is. Subclass of UIViewCo
On Thu, Oct 23, 2014, at 12:25 PM, Alex Zavatone wrote:
> I just started seeing this in Xcode 5.1.1 the post few days under iOS 7.
>
> In the tableView:cellForRowAtIndexPath, you can log the indexPath and the
> results are not nil, but attempting to display [indexPath row] or section
> results in
Hi,
I see a problem on several places in my app. In awakeFromNib, in
restoreStateWithCoder: or just after adding a view programmatically, the bounds
aren’t in sync with the final size or with the super view. The relayout is done
at the end of the runloop. This was not the case in 10.7 but is no
> On Oct 23, 2014, at 2:18 AM, Kevin Meaney wrote:
>
> From what I understand any code that is executed before main is called is
> done so before the objective-c runtime is fully setup which means you have no
> guarantees about what will work. In objective-c++ where you can create static
> C+
On Thu, Oct 23, 2014, at 05:06 PM, Greg Parker wrote:
>
> > On Oct 23, 2014, at 2:18 AM, Kevin Meaney wrote:
> >
> > From what I understand any code that is executed before main is called is
> > done so before the objective-c runtime is fully setup which means you have
> > no guarantees about
> On Oct 23, 2014, at 15:26, Kyle Sluder wrote:
>
> On Thu, Oct 23, 2014, at 05:06 PM, Greg Parker wrote:
>>
>>> On Oct 23, 2014, at 2:18 AM, Kevin Meaney wrote:
>>>
>>> From what I understand any code that is executed before main is called is
>>> done so before the objective-c runtime is fu
> On Oct 23, 2014, at 3:26 PM, Kyle Sluder wrote:
>
>> On Thu, Oct 23, 2014, at 05:06 PM, Greg Parker wrote:
>>
>> The initialization order is generally like this:
>> 1. Everything in libraries you link to is initialized.
>> 2. Your classes' +load methods run. Each class runs +load before its
>
On Oct 23, 2014, at 10:50 AM, Kevin Meaney wrote:
>
> Personally I'd try and not call any objective-c code from a C++ static
> object. If it did look the appropriate solution then I'd make sure I was
> comfortable with my knowledge of the objective-c runtime and the order in
> which things are
11 matches
Mail list logo