• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: String display problems on iPad
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: String display problems on iPad


  • Subject: Re: String display problems on iPad
  • From: Gordon Apple <email@hidden>
  • Date: Sat, 05 Feb 2011 16:40:16 -0600
  • Thread-topic: String display problems on iPad

Thamks.  Looks like 3.2.5 still has a few issues hanging over from 3.2.1.

On my other issue I posted, I fiddled with the database long enough that I
finally got it linking with the right data model, but am now having issues
testing data migration.  (Users are going to be very unhappy if I can't
import their old data.)


On 2/5/11 3:19 PM, "Jerry porter" <email@hidden> wrote:

> Sorry forgot the URL
> http://stackoverflow.com/questions/1427871/xcode-3-2-debug-seeing-whats-in-an-
> array
>
> Sent from my iPad
>
> On Feb 5, 2011, at 16:00, Jerry porter <email@hidden> wrote:
>
>> Here is a blog post that might help.
>> I have not tried it myself
>>
>> Sent from my iPad
>>
>> On Feb 4, 2011, at 14:53, Gordon Apple <email@hidden> wrote:
>>
>>> Why can't the XCode debugger display strings in the variable summary area
>>> when running debug on the iPad? Instead, I get gobbledegook like "{(char
>>> *)Xcode_CFStringSummary($VAR, $ID)}:s".  Not very useful.
>>>
>>> I'm trying to debug some font issues.  It works properly on the simulator.
>>> Also the following does not give me info on the fontNames array (like number
>>> of elements):
>>>
>>>   NSArray* fontFamilyNames = [UIFont familyNames];
>>>   for(NSString* ffName in fontFamilyNames) {
>>>       NSArray* fontNames = [UIFont fontNamesForFamilyName:ffName];
>>>       NSUInteger idx = [fontNames indexOfObject:name];
>>>       if(idx != NSNotFound)
>>>           return YES;
>>>   }
>>>
>>> Is the debugger just that lame when debugging on the device?  Or have I
>>> missed some settings somewhere?
>>>
>>>
>>> _______________________________________________
>>> Do not post admin requests to the list. They will be ignored.
>>> Xcode-users mailing list      (email@hidden)
>>> Help/Unsubscribe/Update your Subscription:
>>>
>>> This email sent to email@hidden
>> _______________________________________________
>> Do not post admin requests to the list. They will be ignored.
>> Xcode-users mailing list      (email@hidden)
>> Help/Unsubscribe/Update your Subscription:
>>
>> This email sent to email@hidden

--
Gordon Apple
Ed4U
Little Rock, AR


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

References: 
 >Re: String display problems on iPad (From: Jerry porter <email@hidden>)

  • Prev by Date: Re: String display problems on iPad
  • Next by Date: Re: Relative Paths
  • Previous by thread: Re: String display problems on iPad
  • Next by thread: Newest Xcode fails on startup
  • Index(es):
    • Date
    • Thread