On 1 Apr 2014, at 3:07 pm, Varun Chandramohan
wrote:
> Ok, Setting it to 1 solved it. Looks like it should not be 0.
Right, it has to be 1. It's annoying that it emits a warning, since this value
is totally ignored AFAICS.
--Graham
___
Cocoa-d
Hi all,
I´m using tableViewSelectionDidChange to find out which row of myTableView was
clicked.
Works fine so far. I´m taking some action than.
- (void)tableViewSelectionDidChange:(NSNotification *)notification
{
NSInteger row = [_tableView selectedRow];
NSLog(@„Row: %il", row);
On Apr 1, 2014, at 12:25 AM, Jens Alfke wrote:
> On Mar 31, 2014, at 10:16 PM, Trygve Inda wrote:
>
>> I need to be able to set a new myDict and not have it happen between the
>> reading of different values from the dictionary by other threads.
>
> Don’t expose the dictionary in mutable form. Y
On Apr 1, 2014, at 12:16 AM, Trygve Inda wrote:
> I have an object with a dictionary property defined as:
>
> @property (nonatomic, retain) NSMutableDictionary* myDict;
>
> This gets set when it is received via an AppleEvent from another
> application.
>
>
>
> Multiple threads in the receivi
On Mar 31, 2014, at 10:16 PM, Trygve Inda wrote:
> I need to be able to set a new myDict and not have it happen between the
> reading of different values from the dictionary by other threads.
Don’t expose the dictionary in mutable form. You can’t make that thread-safe
unless all the clients vo
I have an object with a dictionary property defined as:
@property (nonatomic, retain) NSMutableDictionary* myDict;
This gets set when it is received via an AppleEvent from another
application.
Multiple threads in the receiving app need to read (the threads never write,
only read) from the Dic
Ok, Setting it to 1 solved it. Looks like it should not be 0.
Regards,
Varun
On 1/04/2014 2:57 pm, "Varun Chandramohan"
wrote:
>Hi Graham,
>
>I checked that before posting here. In Size Inspector for ³Box"
>Margins (Horizontal) 0 (Vertical) 0
>Border (Width) 0 (Radius) 0.
>
>That¹s what I am no
Hi Graham,
I checked that before posting here. In Size Inspector for ³Box"
Margins (Horizontal) 0 (Vertical) 0
Border (Width) 0 (Radius) 0.
That¹s what I am not able to understand where the problem is.
- Varun
On 1/04/2014 2:53 pm, "Graham Cox" wrote:
>
>On 1 Apr 2014, at 1:14 pm, Varun Chand
On 1 Apr 2014, at 1:14 pm, Varun Chandramohan
wrote:
> have a view which has a NSBox. The view is designed and managed by IB and I
> am doing nothing from code. The NSBox is of type (primary, the way I want
> it), and border type is Line. When I use this, I get warning "Border width
> requ
Hi All,
I have a view which has a NSBox. The view is designed and managed by IB and I
am doing nothing from code. The NSBox is of type (primary, the way I want it),
and border type is Line. When I use this, I get warning "Border width requires
NSCustomBox type and NSLineBorder" type. To get ri
On Mon, 31 Mar 2014 17:05:30 -0600, Gordon Apple said:
>One thing you are missing, is that, as far as I know, the generated
>accessors are still broken. You have to write your own. I did find a set
>of macros someone wrote for this, but haven1t tried them yet because I had
>already written many
Good to know. Yeah, it was pointed out to me that they aren't generated (STILL?
SERIOUSLY??), but I generated them and now it's all hunky-dory. I'll keep the
other notes you mentioned in mind.
Thanks!
On Mar 31, 2014, at 16:05 , Gordon Apple wrote:
> One thing you are missing, is that, as far
I missed the rest of this thread so I don't know what platform you're on, but
recent OS X has new date/time manipulation functions that can help you with
ensuring you're talking about a valid time. AFAIK, they're not yet in iOS (grr).
On Mar 31, 2014, at 14:31 , Quincey Morris
wrote:
> On Mar
One thing you are missing, is that, as far as I know, the generated
accessors are still broken. You have to write your own. I did find a set
of macros someone wrote for this, but haven¹t tried them yet because I had
already written many of my own sets of accessors.
Two more things to watch out f
On Mar 31, 2014, at 12:04 , D. Felipe Torres wrote:
> I found out it only fails under my current timezone:
I went to stackoverflow to read the outcome, and for completeness I’ll report
here that the above isn’t true.
It doesn’t fail under your particular timezone. It fails under *any* timezone
Your comments have been really helpful. I've done two things to get everything
to work:
Firstly, I turned my triangle upside down, and I set alpha for black at 0.7 and
for white 0.3.
Now it is clear that everything works as it should.
Many Thanks.
Kevin
On 31 Mar 2014, at 20:43, Bill Monk w
> Apple's sample code Image Transition and Cocoa Slides both crash when built
> using Xcode 5.1 and run on 10.9.2
When built with 10.9 SDK, views using CIFilters need their
layerUsesCoreImageFilters set to YES.
Yeah, it bit me too...it's in the 10.9 release notes somewhere.
> But built apps
CIPageCurlTransition's inputBacksideImage does work, but its scaling and/or
interaction with the shading image seems under-documented (to me anyway), and
as such, seems to behave oddly...
But I can definitely get a visible backside image by tweaking your code a
little (using https://gist.githu
On Mon, 31 Mar 2014 04:29:51 -0500, Dado Colussi said:
>> Question: You do some initialization, adding observers for example, in
>> -awakeFromInsert and -awakeFromFetch, and you tear down these
>> initializations, removing observers for example, in -willTurnIntoFault. Do
>> you need to do anythin
I found out it only fails under my current timezone:
I posted the entire thing on stackoverflow:
http://stackoverflow.com/questions/22768918/nsdateformatter-fails-with-string-that-seems-correct
Now all left is finding a workaround
On Mon, Mar 31, 2014 at 3:53 PM, Jens Alfke wrote:
> What OS/v
What OS/version/SDK?
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
ht
Shortly after I replied I tried using that locale and no luck.
My code now looks like this:
NSDateFormatter *formatter = [[NSDateFormatter alloc] init];
[formatter setDateFormat:@"-MM-dd'T'HH:mm:ss"];
NSLocale *locale = [NSLocale localeWithLocaleIdentifier:@"en_US_POSIX"];
[formatter setLocal
Well, try parsing using -getObjectValue:forString:range:error: instead, so you
get an error message.
Also, try setting the locale of the formatter to en_US_POSIX so you don’t get
any localization effects.
(I just got both of these suggestions from “Parsing Date Strings” in Apple’s
“Data Formatti
I just pasted it from CodeRunner.
I changed 00 for 0X where X is a number and it worked.
On Mon, Mar 31, 2014 at 3:09 PM, Jens Alfke wrote:
>
> On Mar 31, 2014, at 10:56 AM, D. Felipe Torres
> wrote:
>
> NSDateFormatter *formatter = [[NSDateFormatter alloc] init];
> [formatter setDateFormat:@"
On Mar 31, 2014, at 10:56 AM, D. Felipe Torres wrote:
> NSDateFormatter *formatter = [[NSDateFormatter alloc] init];
> [formatter setDateFormat:@"-MM-dd'T'HH:mm:ss"];
> NSLog(@"Date from String: %@", [formatter dateFromString:@
> "2013-09-08T00:36:40"]);
>
> The log produces: Date from Stri
Given the following code:
NSDateFormatter *formatter = [[NSDateFormatter alloc] init];
[formatter setDateFormat:@"-MM-dd'T'HH:mm:ss"];
NSLog(@"Date from String: %@", [formatter dateFromString:@
"2013-09-08T00:36:40"]);
The log produces: Date from String: (null)
For other strings from the sam
On Mar 31, 2014, at 11:17 AM, Kevin Meaney wrote:
> Apple's sample code Image Transition and Cocoa Slides both crash when built
> using Xcode 5.1 and run on 10.9.2. But built apps that apple provides with
> the sample code still work on 10.9.2. When built using Xcode 5.1 these
> samples crash
I think this problem might go beyond Core Animation, unless NSAnimation is
using CoreAnimation under the hood.
Apple's sample code Image Transition and Cocoa Slides both crash when built
using Xcode 5.1 and run on 10.9.2. But built apps that apple provides with the
sample code still work on 10.
On 2014 Mar 31, at 02:29, Dado Colussi wrote:
> I don't start observers in -awakeFromInsert or -awakeFromFetch. I start them
> on demand, and in -awakeFromSnapshotEvents: with NSSnapshotEventUndoDeletion
> (I ignore the other flags). I think the best place to start observers depends
> on how
I wrote an application a couple of years ago that still runs perfectly on Mac
OS X 10.7, 10.8 and 10.9. I built it with Xcode 3.x on 10.7. It uses core
animation and layer hosting views.
Now I have to update it for unrelated reasons. But when I build the same code
with Xcode 5.1 on OS X 10.9,
On 29 Mar 2014, at 2:42 PM, Rick Mann wrote:
> Oh, thank you! My googling turned up all sorts of stuff for the "old"
> accessors, but I couldn't find anything about this. I wish they'd generate
> the stubs like they used to.
>
> On Mar 29, 2014, at 09:11 , Rick Aurbach wrote:
>
>> Rick,
>>
On 29 Mar 2014, at 3:11 AM, Rick Mann wrote:
> I'm getting
>
>-[WireSegment replaceObjectInNodesAtIndex:withObject:]: unrecognized
> selector sent to instance
>
> When I try to send that message. This is one of the
> "CoreDataGeneratedAccessors", for an ordered to-many relationship. I don
Thanks for your help.I guess encountering such situations is part of the
job... And I'm still learning it ;-)Colashttps://overview.mail.yahoo.com?.src=iOS";>Envoyé depuis Yahoo
Mail pour iPad
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Plea
Thanks for your input again.
On 31 Mar 2014, at 05:38, Graham Cox wrote:
> OK, I dug out the source code - it's a very old piece of work from when Core
> Image filters were first available. I'm definitely using Curl without a
> shadow.
>
> But, digging into the code,here's the thing - the imag
On 31 March 2014 01:29, Jerry Krinock wrote:
>
> Question: You do some initialization, adding observers for example, in
> -awakeFromInsert and -awakeFromFetch, and you tear down these
> initializations, removing observers for example, in -willTurnIntoFault. Do
> you need to do anything in -awake
On 2014 Mar 31, at 00:06, Kyle Sluder wrote:
> That directly contradicts the -awakeFromInsert documentation, which states
> “This method is invoked only once in the object's lifetime.”
>
> If you are certain you are receiving -awakeFromInsert on the *same*
> NSManagedObject instance, you shou
On Mar 30, 2014, at 11:29 PM, Jerry Krinock wrote:
>
> NSSnapshotEventRollback, if this is due to a deleted object being resurrected
> because the deletion was unsaved. Don't do anything, because you will also
> receive -awakeFromInsert. Seems weird, but that's what happens.
That directly co
37 matches
Mail list logo
