On 05/08/2015 23:28, Steve Mills wrote:
On May 9, 2015, at 00:22:12, Jerry Krinock wrote:
Graham, from one who has been using your code since MacZoop, I say
thank you AGAIN :)
After using Apple’s NSSlider in circular style, I discovered other
issues in addition to the two mentioned in my or
> On 9 May 2015, at 3:22 pm, Jerry Krinock wrote:
>
> Graham, from one who has been using your code since MacZoop, I say thank you
> AGAIN :)
>
> After using Apple’s NSSlider in circular style, I discovered other issues in
> addition to the two mentioned in my original post…
>
> - NSSlider h
> On 10 May 2015, at 1:41 pm, Graham Cox wrote:
>
> I know what you mean about the mouse dragging, it’s a pain when controls seem
> baulky because they expect some complicated motion. I think Howard’s
> suggestion of also interpreting horizontal distance would be a good
> improvement as well,
On May 9, 2015, at 22:44:01, Graham Cox wrote:
>
> P.S. if you can think of any obvious improvements, bugs, etc, let me know.
Personally, I like it when controls also respond to the scrollwheel for inc/dec
actions, like the way active Photoshop fields will inc/dec when you move the
cursor into
> On 10 May 2015, at 2:18 pm, Steve Mills wrote:
>
> I like it when controls also respond to the scrollwheel for inc/dec actions
Me too, which is why it does :)
—Graham
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admi
Although this can be a pain if the control is in a view that also scrolls. I
think some Adobe applications have this issue.
David
> On May 9, 2015, at 11:18 PM, Steve Mills wrote:
>
> On May 9, 2015, at 22:44:01, Graham Cox wrote:
>>
>> P.S. if you can think of any obvious improvements, bug
> On 10 May 2015, at 2:26 pm, David Durkee wrote:
>
> Although this can be a pain if the control is in a view that also scrolls. I
> think some Adobe applications have this issue.
Many apps do, because of the way NSResponder works by passing unhandled events
to the next responder. It happen
On May 9, 2015, at 23:20:08, Graham Cox wrote:
>
> Me too, which is why it does :)
Heh, I didn’t notice that before. One thing I’d suggest: When the knob is set
to stop on tick marks, the scroll event should take it immediately to the
next/prev tick instead of waiting for the float value to ge
