Hi,
Look at this code:
myUserInfo = [self.pUserIDDict objectForKey: theUserInfo.pUserID];
if (myUserInfo != nil)
{
LTWAssertAlways(@"myUserInfo - Dupe ID!!");
}
if (theUserInfo.pUserID != nil)
> On Feb 8, 2016, at 7:15 AM, Dave wrote:
>
> Look at this code:
>
> myUserInfo = [self.pUserIDDict objectForKey: theUserInfo.pUserID];
> if (myUserInfo != nil)
> {
> LTWAssertAlways(@"myUserInfo - Dupe ID!!");
> }
>
> if (theUserInfo.pUserID != nil)
>
> In the case where you do not see a warning, you are calling -[NSDictionary
> objectForKey:] which accepts a nil key value (returning nil).
Ah, for some reason I thought that is was illegal to pass a nil key to
objectForkey:
Thanks
Dave
___
On Feb 8, 2016, at 7:15 AM, Dave wrote:
>
> myUserInfo = [self.pUserIDDict objectForKey: theUserInfo.pUserID];
> if (myUserInfo != nil)
> {
> LTWAssertAlways(@"myUserInfo - Dupe ID!!");
> }
>
> if (theUserInfo.pUserID != nil)
On Feb 8, 2016, at 8:31 AM, Dave wrote:
>
>>
>> In the case where you do not see a warning, you are calling -[NSDictionary
>> objectForKey:] which accepts a nil key value (returning nil).
>
> Ah, for some reason I thought that is was illegal to pass a nil key to
> objectForkey:
It is ill
On Feb 8, 2016, at 10:01 AM, Ken Thomases wrote:
>>>
>>> In the case where you do not see a warning, you are calling -[NSDictionary
>>> objectForKey:] which accepts a nil key value (returning nil).
>>
>> Ah, for some reason I thought that is was illegal to pass a nil key to
>> objectForkey
> On Feb 8, 2016, at 8:09 AM, Steve Sisak wrote:
>
> The nil key pointer is a red herring. -[NSDictionary objectForKey:] can
> return nil if the dictionary doesn’t contain a value for the key.
>
> The analyser is correctly flagging that the code doesn’t handle this case.
No, it isn’t, because
Hello friends. Please pardon this short reprise, but I really need help - maybe
someone can shed some light on my problem.
I’m capturing video using AVFoundation APIs for preview only (OS-X app)
following an old sample-code from Apple (AVRecorder). My view hierarchy is
simple. An NSView (Wants
Hello friends. Please pardon this short reprise, but I really need help - maybe
someone can shed some light on my problem.
I’m capturing video using AVFoundation APIs for preview only (OS-X app)
following an old sample-code from Apple (AVRecorder). My view hierarchy is
simple. An NSView (Wants
On Feb 8, 2016, at 2:41 PM, Motti Shneor wrote:
>
> […] I see strange warnings in the console: "Fallingback to pbuffer. FBO
> status is 36054” for every captured video frame (30 a sec…).
> Can someone tell me what is the source of this error line? what is FBO, and
> what has fallen-back? wher
iOS 9.x, Xcode 7.1.
I'm sitting in the middle of the debugger, looking at some code I inherited and
in a regular service, BLAM, EXC_BAD_ACCESS.
This code uses ivars that are named the same as the properties :/ and what I
noticed, we have this statement where the bad access is appearing:
if ( [
On iOS, we're running into particular issues with one user who puts his device
in Airplane mode overnight.
I'm using reachability classes to determine if we can reach our web services IP
and monitoring all reachability enums, but would be "really nice™" is if there
is a published API to read th
> On Feb 8, 2016, at 13:55, Alex Zavatone wrote:
>
> On iOS, we're running into particular issues with one user who puts his
> device in Airplane mode overnight.
>
> I'm using reachability classes to determine if we can reach our web services
> IP and monitoring all reachability enums, but wo
> On Feb 8, 2016, at 1:47 PM, Alex Zavatone wrote:
>
> if ( [myIVar respondsToSelector:@selector(someMethod)] {
> EXC_BAD_ACCESS (code=1, address=0x143545358)
> I did a po on myiVar and I get an address or 0x00014f05ee00
0x143545358 is probably the (bogus) class-info pointer it got from the
> On Feb 8, 2016, at 1:55 PM, Alex Zavatone wrote:
>
> I'm using reachability classes to determine if we can reach our web services
> IP and monitoring all reachability enums, but would be "really nice™" is if
> there is a published API to read the position of the Airplane Mode setting.
Do yo
I’m trying to implement rather complex UI, with a lot of views involved. The
main window should contain one main view (module), which cannot be removed, and
then users can add arbitrary number of additional specific views (modules) and
arrange them on positions to their liking. Those additional
According to the docs on Reachability (possibly lost in the mists of time...),
Reachability isn't really designed to tell you whether your net access *will*
succeed, but to give you reasons that your last access *failed.*
Yes, I was surprised too, but after adding an initial access to prime the
On Feb 8, 2016, at 15:07 , Dragan Milić wrote:
>
> I’d be very thankful to anyone having the time to look at the video and try
> to figure out what could be the root of the problem. If after watching anyone
> has questions about implementation, code, etc, I’d be happy to provide more
> informa
Thank you so much. You provided all the help I needed. I’ll follow all your
suggestions, and have already opened a DTS with Apple’s own sample code as a
demo of the problem. In past experience with them, If the issue is an Apple bug
- they usually “refund” you a DTS incident.
One curious thing
> On Feb 8, 2016, at 9:45 PM, Glenn L. Austin wrote:
>
> According to the docs on Reachability (possibly lost in the mists of
> time...), Reachability isn't really designed to tell you whether your net
> access *will* succeed, but to give you reasons that your last access *failed.*
It’s not t
20 matches
Mail list logo
