This method is fairly reliable, if your server is fast enough to respond. Something to really watch out for though. If you close the browser and send AJAX request on unload event, there’s a very good chance that the response isn’t going to come back from the server in time before the window object is … Read more
So the OnAppearing event is fired when your page is appearing. I.e. you have navigated to that page or back to that page from another in the Stack. There is currently no Page Lifecycle events as you can see from the API documentation I think what you are talking about is if you put your … Read more
Per the comments, and as already answered, the TextChanged event is not getting raised when you set the Text property to the value it already has. It’s not clear whether this is something you can safely rely upon. It is a sensible optimisation, and I would be very surprised if future versions of .NET Framework … Read more
I’ve been using e.stopImmediatePropagation(); in order to keep the event from propagating. I wish there was a shorter way to do this. I would like return false; but that is due to my familiarity with jQuery
HTML <input ng-click=”some_function($event)”/> JS $scope.some_function = function(event){ if (event.ctrlKey) { // logic here } }
Interesting question. I did some poking around the language notes archive and I discovered that this decision was made on the 13th of October, 1999, but the notes do not give a justification for the decision. Off the top of my head I don’t see any theoretical or practical reason why we could not have … Read more
What initially made this confusing for me is not understanding how the conventions for coding event handlers actually worked versus what was a named variable, combined with the implicit calls done by Javascript handlers when you set up event handlers like this: Good 1 document.getElementById(‘testId’).onkeypress = function(e) { console.log(e.which); } Above, your browser is passing … Read more
Prevent duplicate binding using jQuery’s event namespace There are actually a couple different ways of preventing duplicate. One is just passing the original handler in the unbind, BUT if it is a copy and not in the same space in memory it will not unbind, the other popular way (using namespaces) is a more certain … Read more
This post is quite old, but since I got the same issue. Here is how I solved it (using framework 4.0) : the idea is to use System.Windows.Interactivity. In the XAML : <ComboBox ItemsSource=”{Binding Items}”> <i:Interaction.Triggers> <i:EventTrigger EventName=”SelectionChanged”> <i:InvokeCommandAction Command=”{Binding SelectionChangedCommand}”/> </i:EventTrigger> </i:Interaction.Triggers> </ComboBox> Then you just need to implement the SelectionChangedCommand in your viewmodel.
Use the Closing event in the Window, you can handle it like this to prevent it from closing: private void Window_Closing(object sender, System.ComponentModel.CancelEventArgs e) { e.Cancel = true; }