The internet Lies and other news

Over the last few months I have been slaving away implementing the design for our project. Taken on a lot of responsibility for the client side code. This has been a lot of fun and I have learnt a lot unfortunately I have not learnt how to capture damn ApplicationCommands.

You know the interne? The guy with the tubes, anyway, he told me, on the down low that I could totally treat it like a normal command. -> INCORRECT

after I told him he was a dirty liar, he then told me I could add a new command binding, again incorrect.

I have a theory as to why, I think they ApplicationCommands do no happen to behave like normal RoutedCommand. A routedCommand checks agaisnt itself to see if it has a handler and then fires it at the object with focus and THEN bubbles up the chain.

But I am thinking that the ApplicationCommand does not fire against itself to begin with, instead it goes straight to the object with the Focus, and the object has a built in handler for the command. So before I can even register the command it has fired and executed.

Also, just to make my boss happy

Did you know that mobile safari can only execute Javascript for 5 seconds. It makes sense as javascript only has one ui thread and you could risk not getting control back to your phone.