On May 14, 2015, at 11:52 AM, William Squires wrote:
>
> Oh well, "continue" it is. Though you can still do it manually, if you want!
> :)
While that’s true, fast enumeration performs better.
Charles
___
Cocoa-dev mailing list (Cocoa-dev@lists.appl
I've run into an issue that I haven't seen before with our mapping models: If
the filter predicate was set, and is then cleared, migration complains about
the empty filter predicate with:
NSInvalidArgumentException: Unable to parse the format string ""
I'm having to hand-edit the mappin
This is an entirely different approach, and requires a different skill set, but
could you use JavaScript to inject your content into the DOM of the web page
being displayed as a floating element? Use
stringByEvaluatingJavaScriptFromString: to execute your own JavaScript.
David
> On May 13, 201
With all due respect, I think you’re falling into the common engineer pitfall
of jumping to the conclusion that there’s a trivial solution without first
understanding the problem. (Sometimes expressed as “any bug in your program is
trivial; any bug I have to fix is intractable.”) Which is to say
On May 14, 2015, at 10:52 , Kyle Sluder wrote:
>
> FWIW, NSNotFound is defined as NSIntegerMax, so it has the same value in
> both signed and unsigned contexts.
a. Oh, yeah, I knew that.
b. It kinda proves my point, though. I write enough Obj-C code that I shouldn’t
confuse myself about this,
On May 14, 2015, at 08:40 , William Squires wrote:
>
> I'd like to know how to properly write a value transformer in Swift.
Something like this, I expect:
> class StringNotNilTransformer: NSObject {
>
> static var transformedValueClass: AnyClass { return NSNumber.self }
> sta
On Thu, May 14, 2015, at 12:34 PM, Quincey Morris wrote:
> — It’s used in both signed and unsigned contexts, so it really has 2
> values
FWIW, NSNotFound is defined as NSIntegerMax, so it has the same value in
both signed and unsigned contexts.
--Kyle Sluder
_
On May 14, 2015, at 09:50 , William Squires wrote:
>
> Have the compiler/linker enforce that all variables are initialized to zero
> (Int, Float, Double), false (Bool), empty (String, array, dictionary), or nil
> (object reference) if the coder doesn't specify them. (in the case of an
> enume
Oh well, "continue" it is. Though you can still do it manually, if you want! :)
On May 14, 2015, at 11:15 AM, William Squires wrote:
> Not as far as I know; this is one of those times when you're better off doing
> a manual loop with a regular for( ; ; ) {} statement; then you can test the
> l
or, to put it another way; "optional Optionals, a better " :)
Option 1 (1?):
Have the compiler/linker enforce that all variables are initialized to zero
(Int, Float, Double), false (Bool), empty (String, array, dictionary), or nil
(object reference) if the coder doesn't specify them. (in the c
Just tested Mike's suggestion and "continue" does the trick.
Here's a test that verifies that..
NSArray *myStuff = [[NSArray alloc]initWithObjects:@"A", @"B", @"Puppies",
@"C",@"D", nil];
for (NSString *myThing in myStuff) {
if ([myThing isEqualToString:@"Puppies"]) {
'continue’
Just like other c loop constructs.
> On 15 May 2015, at 12:09 am, Alex Zavatone wrote:
>
> I'm sure this will sound like the noobiest question ever, but with Fast
> Enumeration, if in an if statement within the loop, is there a way to stop
> loop execution and essentially do a "
Not as far as I know; this is one of those times when you're better off doing a
manual loop with a regular for( ; ; ) {} statement; then you can test the loop
iterator with a switch() and take appropriate action (or none at all, if
desired.)
On May 14, 2015, at 11:09 AM, Alex Zavatone wrote:
You want:
continue;
Same as a regular for loop in C.
> On 14 May 2015, at 18:09, Alex Zavatone wrote:
>
> I'm sure this will sound like the noobiest question ever, but with Fast
> Enumeration, if in an if statement within the loop, is there a way to stop
> loop execution and essentially do a
I'm sure this will sound like the noobiest question ever, but with Fast
Enumeration, if in an if statement within the loop, is there a way to stop loop
execution and essentially do a "proceed to the next item in the list please"?
Interested in something like BASIC's next repeat or something to t
Thanks, I didn't even think of that, but yeah, it would be easier. Still, I'd
like to know how to properly write a value transformer in Swift.
On May 12, 2015, at 5:38 PM, Quincey Morris
wrote:
> On May 12, 2015, at 14:29 , William Squires wrote:
>>
>> class IsNotEmptyTransformer : NSValueTr
I've tried 2 and didn't work. How do I do 1?
On Thu, May 14, 2015 at 7:46 AM, Uli Kusterer
wrote:
> Two things I’d try:
>
> 1) Make your view layer-backed
> 2) Ensure that your view is a peer, not a subview of the web view.
>
> Any of that your issue?
>
> > On 14 May 2015, at 03:31, Juanjo Conti
Two things I’d try:
1) Make your view layer-backed
2) Ensure that your view is a peer, not a subview of the web view.
Any of that your issue?
> On 14 May 2015, at 03:31, Juanjo Conti wrote:
>
> I'm writing a screen saver, so using another window is not possible :(
>
> On Tue, May 12, 2015 at
> On 14 May 2015, at 03:43, Michael David Crawford wrote:
>
> would it work render the web view in an offscreen buffer, then copy
> that onto an on-screen view of your own?
>
> At that point you could either have your child view, or simply draw
> into one big view.
That works for much web cont
19 matches
Mail list logo
