<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>TextBlock on DVLUP</title><link>/en/tags/textblock/</link><description>Recent content in TextBlock on DVLUP</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 02 Jan 2020 00:00:00 +0000</lastBuildDate><atom:link href="/en/tags/textblock/index.xml" rel="self" type="application/rss+xml"/><item><title>Custom TypingStarted and TypingEnded Events</title><link>/en/blog/2020.01.02-custom-typingstarted-and-typingended-events/</link><pubDate>Thu, 02 Jan 2020 00:00:00 +0000</pubDate><guid>/en/blog/2020.01.02-custom-typingstarted-and-typingended-events/</guid><description>&lt;p&gt;You know that little indicator in a chat that shows if someone is currently typing? I am working on a new post (coming soon, link will be here) that uses SignalR to communicate who is currently typing in a chat room along with the messages themselves.&lt;/p&gt;&#10;&lt;p&gt;To determine who is typing, I use a timer and the &lt;code&gt;TextChanged&lt;/code&gt; event. The timer logic itself is straightforward, in the &lt;code&gt;TextChanged&lt;/code&gt; event starts a timer.&lt;/p&gt;</description></item><item><title>Read-only Address Bar for Webview</title><link>/en/blog/2014.10.26-read-only-address-bar-for-webview/</link><pubDate>Sun, 26 Oct 2014 00:00:00 +0000</pubDate><guid>/en/blog/2014.10.26-read-only-address-bar-for-webview/</guid><description>&lt;p&gt;If you are having a Windows Store application fail certification or being unpublished because you have violated &lt;strong&gt;Policy 2.1.2&lt;/strong&gt;  - &lt;em&gt;requires a visible address bar that displays a secure connection to users when they enter financial information or complete a transaction&lt;/em&gt; (&lt;a href="http://msdn.microsoft.com/en-us/library/windows/apps/hh184841%28v=vs.105%29.aspx" target="_blank" rel="noopener"&gt;see policy definitions&lt;/a&gt;&#10;).&lt;/p&gt;&#10;&lt;p&gt;The reason for this rule is because you are bringing the user to a site that is using HTTPS and the user may be entering in secure information. You &lt;strong&gt;need to give the user confidence&lt;/strong&gt; that you are not spoofing the website and stealing the entered information.&lt;/p&gt;</description></item></channel></rss>