Advanced Forum Search Results
-
It's been few months now but in case someone is still looking at a solution, I have followed these instructions and it has worked.
http://www.codeproject.com/KB/WCF/WCFBasicHttpBinding.aspx
-
Indeed, peluchejs is right, that won't work. OriginalSouce is the control that loose the focus. In this case, it will always return Popup control since the LostFocus event is always fired by Popup (it's the only control I have attached to LostFocus event to).
Btw, I have done an extension method for this:
public static bool ...
-
Excellent, that does the trick! Thanks
-
Hi,
I use a Popup control that contains two Textbox controls. The Popup should close automatically when it looses focus (same as a dropdown menu). So, I catch Popup's LostFocus and close the Popup control (that works). The problem here is that the first Textbox fires a LostFocus event when I switch to the second Texbox and the Popup catches ...
-
Yup, sorry, I forgot to mention initially that I attach the event to the "BODY", not a specific element.
-
Maybe I should have titled this "Differences between browsers"... anyway, just got this one, if you need to remove the "class" attribute
IE6 : htmlElement.RemoveAttribute("className"); (tested in IE6 only, maybe it works in IE7?)
FF : htmlElement.RemoveAttribute("class");
-
I know Mozilla has a different "event model" that "bubbles" from the root to the top but shouldn't Silverlight's HtmlEventArgs.Source returns the last affected element instead of the root element (as if I would call "target")? Now I need to do a "check" and call ...
-
Ok, I'll undust it and see if I get the same result...
When you set request.Method to POST, can you see the "custom" header (name and value) on the server side?
-
Hi, what you described in your initial request is exactly what I was trying to do... I got it to work at the end but not without pain. I haven't touched the code since then though because I was waiting to see what would happened after beta2... Let me know how it will end up on your side! :)
Regards,
Pat
-
Thanks for the answer... I should have mentioned that I'm using SL2 Beta2. Isolated Storage is volatile in SL1 (associated with browser cache), not in Beta2... Anyway, that is not my problem since the data is still there, on the hard drive... and it's not a "problem", just a glitch with beta version I suppose... I was just ...