Hi all,
I feel this should be a very simple question, but I am struggling with it - the
tutorials and online info I can find is either 5 years out of date or seem to
imply that I am doing everything right!
In my code I have an NSMutableArray of “message” objects, each with a number of
properti
Ah brilliant, that’s fixed it - thanks very much! Makes sense in retrospect
that I would have to do that, but hadn’t crossed my mind at the time.
Cheers
Jonny
On 23 Sep 2014, at 17:26, Marek Hrušovský wrote:
> This sounds like that selection from nstableview is not properly linked. Make
> sure
> On Sep 22, 2014, at 7:16 PM, Herman Chan wrote:
>
> Hi Ben,
>
> I have both in my app, both presenting from rootVC and just plain controller.
> I fish out the rootVC to get rid of warning like this "Presenting view
> controllers on detached view controllers is discouraged”.
So why do you
Hi David,
Here is my set up in term of view controllers.
- (void) setUpTabbarController {
self.tabBarController = [[MyTabbarViewController alloc] init];
ViewController *v1 = [[HubActivityViewController alloc]
initWithNibName:nil bundle:nil];
ViewController *v2 = [[CalendarContainerViewCo
> On Sep 23, 2014, at 10:45 AM, Herman Chan wrote:
>
> Hi David,
>
> Here is my set up in term of view controllers.
>
> - (void) setUpTabbarController {
>
> self.tabBarController = [[MyTabbarViewController alloc] init];
> ViewController *v1 = [[HubActivityViewController alloc] initWithNibNa
> On Sep 22, 2014, at 11:02 PM, Rick Mann wrote:
>
>> On Sep 22, 2014, at 18:38 , Roland King wrote:
>>
>>> On 23 Sep 2014, at 9:20 am, Rick Mann wrote:
>>>
>>> I tried to find some documentation of a change, but can't It seems that the
>>> statusBarFrame returned in iOS 8 is different than
Hi David,
Yes, it was related to the PPRevealSideViewController, which I'll look
into to see if I can fix it.
However, I don't know if that's the problem with my original problem.
That warning for detached view controller has been there for awhile
through iOS 6 -> 7 and it has been fine for
> On Sep 23, 2014, at 11:19 AM, Herman Chan wrote:
>
> Hi David,
>
> Yes, it was related to the PPRevealSideViewController, which I'll look into
> to see if I can fix it.
>
> However, I don't know if that's the problem with my original problem.
>
> That warning for detached view controller h
Hi David,
Thanks! I wish I can reproduce this, but that's life.
I'll try to get rid of the warning and see if it still crash in the
wild.
herman
On 23 Sep 2014, at 14:25, David Duncan wrote:
On Sep 23, 2014, at 11:19 AM, Herman Chan
wrote:
Hi David,
Yes, it was related to the PPReveal
Hi all,
Another mysterious iOS 8 crash I am getting, here is the crash log.
Thread : Crashed: com.apple.main-thread
0 libobjc.A.dylib0x32bfbf46 objc_msgSend + 5
1 UIKit 0x289ba531 -[UIWindow
_updateInterfaceOrientationFromDeviceOrientation:] + 152
2 C
On Sep 23, 2014, at 9:15 AM, Jonathan Taylor
wrote:
>
>
>
>
> [*] One slight glitch - if I add an object to the NSMutableArray then it does
> not immediately show up in the table, I have to call
> will/didChangeValueForKey on the property that returns the array. I don’t
> know if that is
On Sep 23, 2014, at 11:36 , Lee Ann Rucker wrote:
> On Sep 23, 2014, at 9:15 AM, Jonathan Taylor
> wrote:
>>
>> [*] One slight glitch - if I add an object to the NSMutableArray then it
>> does not immediately show up in the table, I have to call
>> will/didChangeValueForKey on the property t
I do, and did, but it's ever-more-demoralizing to report bugs and just have
them fall into a black hole (which is how it feels for the vast majority of
bugs. They're either duplicates, or "behaves as designed," and they rarely get
fixed).
Doc feedback is worse, because there's no way to track t
> On Sep 23, 2014, at 11:31 AM, Herman Chan wrote:
>
> Hi all,
>
> Another mysterious iOS 8 crash I am getting, here is the crash log.
>
> Thread : Crashed: com.apple.main-thread
> 0 libobjc.A.dylib0x32bfbf46 objc_msgSend + 5
> 1 UIKit 0x289ba531 -[UI
Thankyou both for your advice - it's good to have you set me right on that one.
Fortunately mine is a relatively uncomplicated case, and so [NSArrayController
add/removeObject:] should do the job nicely
It feels a bit odd doing it that way, just because it makes the NSArray almost
redundant in
In iOS 7, my app works fine. In iOS 8, deleting an entity eventually works, but
whereas in iOS 7 my UI would update and show the change, the change doesn't
seem to have "taken hold" by this time in iOS 8.
Basically, when the user deletes an entity, I delete it from the MOC (main
thread), then m
I was trying to fix some (what I thought to be) minor alignment bugs that
came up during QA for one of our apps, when I stumbled on one of the more
strange bugs I've seen recently.
In this app, the first screen presents you with the options to log in or
create an account.
The login screen is two t
On Sep 23, 2014, at 4:24 PM, Rick Mann wrote:
>
> In iOS 7, my app works fine. In iOS 8, deleting an entity eventually works,
> but whereas in iOS 7 my UI would update and show the change, the change
> doesn't seem to have "taken hold" by this time in iOS 8.
>
> Basically, when the user delete
I have a problem with NSLinguisticTagger / CFStringTokenizer on iOS 8.0
OS X 10.9.5 (and iOS 7 and earlier) parses "สีเหลือง" quite rightly as two
words: "สี" = colour and "เหลือง" = yellow.
No dictionary will ever contain "yellow colour". Every dictionary will contain
"yellow" and "colour".
Th
> On 24 Sep 2014, at 12:31 pm, Gerriet M. Denkmann wrote:
>
> I have a problem with NSLinguisticTagger / CFStringTokenizer on iOS 8.0
>
> OS X 10.9.5 (and iOS 7 and earlier) parses "สีเหลือง" quite rightly as two
> words: "สี" = colour and "เหลือง" = yellow.
>
> No dictionary will ever contai
On 24 Sep 2014, at 11:46, Roland King wrote:
>
>> On 24 Sep 2014, at 12:31 pm, Gerriet M. Denkmann
>> wrote:
>>
>> I have a problem with NSLinguisticTagger / CFStringTokenizer on iOS 8.0
>>
>> OS X 10.9.5 (and iOS 7 and earlier) parses "สีเหลือง" quite rightly as two
>> words: "สี" = colou
> On 24 Sep 2014, at 1:02 pm, Gerriet M. Denkmann wrote:
>
>
> On 24 Sep 2014, at 11:46, Roland King wrote:
>
>>
>>> On 24 Sep 2014, at 12:31 pm, Gerriet M. Denkmann
>>> wrote:
>>>
>>> I have a problem with NSLinguisticTagger / CFStringTokenizer on iOS 8.0
>>>
>>> OS X 10.9.5 (and iOS 7
On 24 Sep 2014, at 12:23, Roland King wrote:
>
>> On 24 Sep 2014, at 1:02 pm, Gerriet M. Denkmann wrote:
>>
>>
>> On 24 Sep 2014, at 11:46, Roland King wrote:
>>
>>>
On 24 Sep 2014, at 12:31 pm, Gerriet M. Denkmann
wrote:
I have a problem with NSLinguisticTagger / C
23 matches
Mail list logo
