Re: NSCursor tracking areas

2014-07-24 Thread Cody Garvin
Tried to send this yesterday with code, but I guess it was too big. This is on Xcode 6 Beta 4 / OS X 10.10. The app is built for 10.10, so perhaps a bug. I’m getting some randomness with updating the cursor. Sometimes works as intended, sometimes not. I have four hotspots on the corners of se

Re: NSCursor tracking areas

2014-07-24 Thread edward taffel
On Jul 24, 2014, at 9:37 AM, Cody Garvin wrote: > Tried to send this yesterday with code, but I guess it was too big. > > This is on Xcode 6 Beta 4 / OS X 10.10. The app is built for 10.10, so > perhaps a bug. > > I’m getting some randomness with updating the cursor. Sometimes works as > int

Re: NSCursor tracking areas

2014-07-24 Thread Cody Garvin
> > is it set (enter), reset (exit), or both that sometimes do not work as > intended? > Setting it, resetting seems to always work. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to th

Re: NSCursor tracking areas

2014-07-24 Thread edward taffel
On Jul 24, 2014, at 10:18 AM, Cody Garvin wrote: >> >> is it set (enter), reset (exit), or both that sometimes do not work as >> intended? >> > > Setting it, resetting seems to always work. ah, well, i had a similar problem, but the opposite. have you tried doing the set in mouseEntered?

Re: NSCursor tracking areas

2014-07-24 Thread Cody Garvin
> > ah, well, i had a similar problem, but the opposite. have you tried doing the > set in mouseEntered? > I have not tried mouseEntered yet. If I go that route, should I dispose of cursorUpdate? - Cody ___ Cocoa-dev mailing list (Cocoa-dev@lists.

Re: NSCursor tracking areas

2014-07-24 Thread edward taffel
On Jul 24, 2014, at 10:30 AM, Cody Garvin wrote: > >> >> ah, well, i had a similar problem, but the opposite. have you tried doing >> the set in mouseEntered? >> > > I have not tried mouseEntered yet. If I go that route, should I dispose of > cursorUpdate? > > - Cody of course, you’ll ne

Re: NSCursor tracking areas

2014-07-24 Thread Ken Thomases
On Jul 24, 2014, at 8:37 AM, Cody Garvin wrote: > I use updateTrackingAreas to remove all the tracking areas, then adding new > ones (same rects as the drag points) with the options: > NSTrackingActiveInActiveApp | NSTrackingCursorUpdate | NSTrackingAssumeInside Why are you including NSTrackin

Re: NSCursor tracking areas

2014-07-24 Thread Cody Garvin
> On Jul 24, 2014, at 7:40 AM, Ken Thomases wrote: > > On Jul 24, 2014, at 8:37 AM, Cody Garvin wrote: > >> I use updateTrackingAreas to remove all the tracking areas, then adding new >> ones (same rects as the drag points) with the options: >> NSTrackingActiveInActiveApp | NSTrackingCursorU

NSStream's enum of NSStreamEventEndEncountered.

2014-07-24 Thread Alex Zavatone
In Xcode 5.1.1 and coding for iOS 7, I was just wondering why not all of NSStream's enums are able to be caught in a switch/case statement in the NSStreamDelegate In - (void)stream:(NSStream *)theStream handleEvent:(NSStreamEvent) streamEvent, I'll log streamEvent and in the case of 4, which

Re: NSStream's enum of NSStreamEventEndEncountered.

2014-07-24 Thread Sean McBride
On Thu, 24 Jul 2014 14:05:17 -0400, Alex Zavatone said: >If I change > >case NSStreamEventEndEncountered: > >to > >case 4: > >the event is caught. > >Since NSStreamEventEndEncountered is supposed to = 1UL << 4 in the >NSStream header, does anyone have any idea what's going on here? Um,

Re: NSStream's enum of NSStreamEventEndEncountered.

2014-07-24 Thread Ken Thomases
On Jul 24, 2014, at 1:05 PM, Alex Zavatone wrote: > - (void)stream:(NSStream *)theStream handleEvent:(NSStreamEvent) streamEvent, > > I'll log streamEvent and in the case of 4, which is is supposed to be > typdefed to NSStreamEventEndEncountered, it's never trapped at all. NSStreamEventEndEnc

Re: NSStream's enum of NSStreamEventEndEncountered.

2014-07-24 Thread edward taffel
On Jul 24, 2014, at 2:45 PM, Sean McBride wrote: > On Thu, 24 Jul 2014 14:05:17 -0400, Alex Zavatone said: > >> If I change >> >> case NSStreamEventEndEncountered: >> >> to >> >> case 4: >> >> the event is caught. >> >> Since NSStreamEventEndEncountered is supposed to = 1UL << 4 in t

Re: NSStream's enum of NSStreamEventEndEncountered.

2014-07-24 Thread Alex Zavatone
On Jul 24, 2014, at 2:46 PM, Ken Thomases wrote: > On Jul 24, 2014, at 1:05 PM, Alex Zavatone wrote: > >> - (void)stream:(NSStream *)theStream handleEvent:(NSStreamEvent) >> streamEvent, >> >> I'll log streamEvent and in the case of 4, which is is supposed to be >> typdefed to NSStreamEvent

Re: NSStream's enum of NSStreamEventEndEncountered.

2014-07-24 Thread Quincey Morris
On Jul 24, 2014, at 11:58 , edward taffel wrote: > NSStreamEventOpenCompleted = 1 << 0, > > a point of style? Supposition: It’s point of API self-documentation. The shift indicates that this is a bit mask (or bit field) value, and hence that the enum’s members can usefully be OR’ed together.

Re: NSStream's enum of NSStreamEventEndEncountered.

2014-07-24 Thread Alex Zavatone
On Jul 24, 2014, at 4:43 PM, Quincey Morris wrote: > On Jul 24, 2014, at 11:58 , edward taffel wrote: > >> NSStreamEventOpenCompleted = 1 << 0, >> >> a point of style? > > Supposition: > > It’s point of API self-documentation. The shift indicates that this is a bit > mask (or bit field) val

Re: NSCursor tracking areas

2014-07-24 Thread Cody Garvin
> On Jul 24, 2014, at 1:51 PM, Markus Spoettl wrote: > > On 24/07/14 15:37, Cody Garvin wrote: >> I then use cusrorUpdate:(NSEvent *)theEvent to change the cursor by iterating >> over theEvent’s converted point to the view and matching it with a drag point >> (I do this because in the future the

Re: NSCursor tracking areas

2014-07-24 Thread Quincey Morris
On Jul 24, 2014, at 14:35 , Cody Garvin wrote: > I think I’ll try your’s and Edward’s suggestion on attempt mouseEntered / > mouseMoved with a single tracking area. From one point of view, I would recommend *not* taking this approach, since it comes near to flailing, and that’s never a good wa

NSView in 10.10

2014-07-24 Thread Graham Cox
Looking at the lastest documentation for Yosemite, is indicates that -[NSView isFlipped] is deprecated. That seems rather major. Does that mean we can't have flipped views in future? Otr is something replacing this? --Graham ___ Cocoa-dev mailing l

Re: NSView in 10.10

2014-07-24 Thread Kyle Sluder
On Thu, Jul 24, 2014, at 06:39 PM, Graham Cox wrote: > Looking at the lastest documentation for Yosemite, is indicates that > -[NSView isFlipped] is deprecated. That seems rather major. Does that > mean we can't have flipped views in future? Otr is something replacing > this? It's not deprecated;

Re: NSView in 10.10

2014-07-24 Thread Eric E Dolecki
http://prod.lists.apple.com/archives/quartz-dev/2014/Jul/msg3.html Eric > On Jul 24, 2014, at 7:39 PM, Graham Cox wrote: > > Looking at the lastest documentation for Yosemite, is indicates that -[NSView > isFlipped] is deprecated. That seems rather major. Does that mean we can't > have fl

Re: NSView in 10.10

2014-07-24 Thread Cody Garvin
They did this as a migration to Swift I believe. It has to do with migrating to properties from getters / setters. If you look at the header, the property is now just flipped, and readonly. However, you can still override the getter method on the property itself and return YES. - Cody > On J

Re: NSView in 10.10

2014-07-24 Thread Graham Cox
On 25 Jul 2014, at 9:44 am, Kyle Sluder wrote: > It's not deprecated; it was just converted to a read-only property. Thanks - makes sense. #relieved --Graham ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests