I’m exploring the use of the new IB_DESIGNABLE macro to preview a custom view
live in IB.
It keeps complaining that my view is taking too long to draw, over 200mS, which
seems to be a limit built into IB. However, when I measure the time myself for
drawing, it’s nowhere near this long - 10mS ma
> On 11 May 2015, at 9:41 pm, Graham Cox wrote:
>
>
>> On 11 May 2015, at 9:25 pm, Roland King wrote:
>>
>>
>> I thought they added phase and momentumPhase to NSEvent, plus
>> hasPreciseScrollingDeltas, scrollingDeltaX and scrollingDeltaY to help
>> disambiguate between clicky scrollwheels
Yeah, I'm adding that to my code now. Thank you :)
On Mon, May 11, 2015 at 2:10 PM, Ryan Dignard
wrote:
> It may be advantage to log whether the model file exists and if it does
> exist if the permissions are correct.
>
> On Mon, May 11, 2015 at 1:06 PM, Alex Kac wrote:
>>
>> So I've only seen t
It may be advantage to log whether the model file exists and if it does
exist if the permissions are correct.
On Mon, May 11, 2015 at 1:06 PM, Alex Kac wrote:
> So I've only seen this on OS X crashlytics, but one of my engineers
> says he's seen some logs on iOS as well. So I'm not calling it an
So I've only seen this on OS X crashlytics, but one of my engineers
says he's seen some logs on iOS as well. So I'm not calling it an OS X
only issue yet.
It would be interesting to see if this happens only on updates or new
installs though… Great idea! Thanks.
On Mon, May 11, 2015 at 2:03 PM, Mi
> On 11 May 2015, at 21:43, Alex Kac wrote:
>
> We have an app that's out in the wild, and as always there are weird
> issues that sometimes show up then. This seems like it should never
> happen or always happen.
>
> The crash is here:
>
> http://crashes.to/s/f382ed6e4ef
>
> Obviously we ha
We have an app that's out in the wild, and as always there are weird
issues that sometimes show up then. This seems like it should never
happen or always happen.
The crash is here:
http://crashes.to/s/f382ed6e4ef
Obviously we have a working model…its been shipped and working in
hundreds of thous
> On 11 May 2015, at 9:25 pm, Roland King wrote:
>
>
> I thought they added phase and momentumPhase to NSEvent, plus
> hasPreciseScrollingDeltas, scrollingDeltaX and scrollingDeltaY to help
> disambiguate between clicky scrollwheels and draggy trackpads, give finer
> results and let you know
> On 11 May 2015, at 18:26, Graham Cox wrote:
>
>
>> On 11 May 2015, at 7:15 pm, dangerwillrobinsondan...@gmail.com wrote:
>>
>> It still receives the same events that are sent from scrolling.
>
>
> I entirely understand that.
>
>
>> All the same things apply about interpreting the events
> On 11 May 2015, at 7:15 pm, dangerwillrobinsondan...@gmail.com wrote:
>
> It still receives the same events that are sent from scrolling.
I entirely understand that.
> All the same things apply about interpreting the events that pass in to the
> scrollWheel: method.
> It is your gateway
You've missed something.
NSScrollView coordinates the scrollers and the clip view total experience.
NSView is what implements the NSResponder method.
It still receives the same events that are sent from scrolling.
All the same things apply about interpreting the events that pass in to the
sc
> On 11 May 2015, at 2:27 pm, dangerwillrobinsondan...@gmail.com wrote:
>
> There was a WWDC video on Responsive Scrolling.
If that’s the one from WWDC 2013 that talks about
NSScrollViewDidLiveScrollNotification and friends, I don’t think it’s relevant
to this situation.
If you have a view
12 matches
Mail list logo
