On 29/08/2013, at 5:18 AM, Rick C. wrote:
> But this is an unreliable way to do this I know because I have problems. Can
> someone please help me with the right way? Because I need for it to wait
> before advancing or else it will cause problems in following code. Really
> appreciate the t
Hi,
Not sure why I am struggling here but if someone could assist me that would be
great. In one part of my code I'm calling this:
[prefs setObject:[self userImage:[i valueForKey:@"username"] whichAccount:i]
forKey:@"User Image"];
Which will in turn call this:
- (UIImage *)userImage:(NSStrin
Are those really always constant? Why not:
NSCharacterSet *stopCharacters = [NSCharacterSet
characterSetWithCharactersInString:@"< \t\n\r\x85\x0C\u2028\u2029"];
On Wed, Aug 28, 2013 at 3:26 PM, Dave wrote:
> Hi,
>
> I am getting the following warning
>
> warning: format specifies type 'unsigne
On Aug 28, 2013, at 4:51 PM, Boyd Collier wrote:
> I think I understand what the problem is and the fix, but what does the <
> following the opening quote signify?
It’s just a literal “<“ character in the string; nothing magic. (The code looks
like it’s constructing an NSCharacterSet, and “<“
I think I understand what the problem is and the fix, but what does the <
following the opening quote signify?
Boyd
On Aug 28, 2013, at 1:30 PM, Tom Davie wrote:
>
> On 28 Aug 2013, at 22:26, Dave wrote:
>
>> Hi,
>>
>> I am getting the following warning
>>
>> warning: format specifies t
Thanks again Dru,Tom, Diederik and everyone who chimed in with your
valuable insights. I have made a list of action items from each of your
feedback. Back to the kitchen to cook up something nice. Hopefully you guys
wont be disappointed next time I come back here.
Feel free to message me directly
On 28 Aug 2013, at 22:26, Dave wrote:
> Hi,
>
> I am getting the following warning
>
> warning: format specifies type 'unsigned short' but the argument has type
> 'int' [-Wformat]
>
> on this statement:
>
> NSCharacterSet *stopCharacters = [NSCharacterSet
> characterSetWithCharactersInStr
Hi,
I am getting the following warning
warning: format specifies type 'unsigned short' but the argument has type 'int'
[-Wformat]
on this statement:
NSCharacterSet *stopCharacters = [NSCharacterSet
characterSetWithCharactersInString:[NSString stringWithFormat:@"<
\t\n\r%C%C%C%C", 0x0085, 0x
On Aug 28, 2013, at 4:53 PM, Marcel Weiher wrote:
> does anyone have practical experience with the forward/backward compatibility
> aspect of keyed archiving? That is define a file format using keyed
> archiving where backward and forward compatibility was both desirable and
> achieved?
Hi,
On Aug 28, 2013, at 8:53 AM, Marcel Weiher wrote:
> does anyone have practical experience with the forward/backward compatibility
> aspect of keyed archiving? That is define a file format using keyed
> archiving where backward and forward compatibility was both desirable and
> achieved?
Do yo
Hi folks,
does anyone have practical experience with the forward/backward compatibility
aspect of keyed archiving? That is define a file format using keyed archiving
where backward and forward compatibility was both desirable and achieved?
Thanks!
Marcel
On 28/08/2013, at 2:22 PM, Marcel Weiher wrote:
> Well, first you have a /Font. This should contain a reference to a
> /FontDescriptor. If the font is embedded in the file, then you have a
> /FontFile reference ( or /FontFile1, /FontFile2, /FontFile3), which then
> points to the PDF Stream
On Aug 27, 2013, at 14:46 , Graham Cox wrote:
> Parsing a PDF, I need to handle the Tf (set font) operator. The font
> situation in PDF files is inordinately complicated, and reading the spec
> alone is not really leading to the light-bulb moment.
Yes, there are many dark tunnels ahead...
>
And do yourself a huge favor. Repeat to yourself every morning (and anytime
you get frustrated), "Developers are friends not food".
I use that analogy intentionally, you are selling to the most critical market
you will ever sell to. Not just other developers, which is bad enough, but
Apple/iO
For reference, I’m not convinced that you needed them here, but instead, that
you didn’t devote enough thought to how that UI should work on a touch screen.
There’s no reason why your preferences couldn’t have used a column of
UISwitches. Your export panel could have used a UISegmentedControl
15 matches
Mail list logo
