Hi Alastair,
Thanks a lot for this - it makes my life harder but at least I know how it
works now.
All the Best
Dave
> On 17 Jul 2016, at 21:03, Alastair Houghton
> wrote:
>
> On 17 Jul 2016, at 14:06, Dave wrote:
>>
>> My question is, do the keyboard and Mouse Down Events come in pairs, s
Fair enough, thanks! I would say then yes, it’s a mismatch between the docs and
the implementation.
File a radar, but don’t expect the real-world behaviour to change, especially
any time soon! It’s far more likely they will declare it to be a mistake in the
docs and correct those.
Mike.
> On
You might review the Event programming guide (especially the part about short
circuiting) and the responder chain.
That will pull this together in some detail.
Sent from my iPhone
> On Jul 18, 2016, at 7:57 PM, Dave wrote:
>
> Hi Alastair,
>
> Thanks a lot for this - it makes my life harder
Hi,
Thanks, I’m looking at it now.
I’m a bit confused over the keyboard handling. I would have thought that the
processing would take place on the KeyUp event, but it seems like its occurring
on the KeyDown event which is where I am going wrong.
I’m not sure what use NSKeyUp is in this case?
On Jul 18, 2016, at 07:52:02, Dave wrote:
>
> Hi,
>
> Thanks, I’m looking at it now.
>
> I’m a bit confused over the keyboard handling. I would have thought that the
> processing would take place on the KeyUp event, but it seems like its
> occurring on the KeyDown event which is where I am go
To be fair, iOS and mouse events tend to finish on the concept of up.
(Though often it's up & inside to trigger some action)
Sent from my iPhone
> On Jul 18, 2016, at 10:00 PM, Steve Mills wrote:
>
>> On Jul 18, 2016, at 07:52:02, Dave wrote:
>>
>> Hi,
>>
>> Thanks, I’m looking at it now.
>
Yes, I guess because in this case then is the possibility of the Mouse/Finger
moving outside the Control between the Down and Up events…...
> On 18 Jul 2016, at 14:05, dangerwillrobinsondan...@gmail.com wrote:
>
> To be fair, iOS and mouse events tend to finish on the concept of up.
> (Though o
Hi all,
I have an application which installs and uses a privileged helper tool that,
for myself and most users, seems to work just fine.
I do, however, have one user (and experience tells me there'll be more who
simply aren't reporting it) who's experiencing my app crashing when
communicating
I found another solution: set the header search paths in the test target so
it can find the App-Swift.h file from the app target, include that in the
ObjC tests that need the Swift classes (instead of the one generated for
the test target), and then remove all the app Swift files from the test
targ
I have an application that occasionally deadlocks with the main thread calling
-[NSViewHierarchyLock _lockForWriting:handler:] and no other thread stack
showing any operation in progress that might need to own this lock. I saved a
core dump. Is there any way I can poke around in the core dump us
On Jul 18, 2016, at 7:37 AM, Mike Abdullah wrote:
> Fair enough, thanks! I would say then yes, it’s a mismatch between the docs
> and the implementation.
>
> File a radar, but don’t expect the real-world behaviour to change, especially
> any time soon! It’s far more likely they will declare i
11 matches
Mail list logo
