<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>John C. Bland II - My Thoughts and Ramblings - Latest Comments</title><link>http://johncblandii.disqus.com/</link><description></description><atom:link href="https://johncblandii.disqus.com/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Wed, 28 Mar 2018 06:12:29 -0000</lastBuildDate><item><title>Re: React-Native Pin Entry View with a Custom Keyboard</title><link>http://johncblandii.com/2017/05/react-native-pin-entry-view-with-a-custom-keyboard.html#comment-3828006172</link><description>&lt;p&gt;undefined is not an object (evaluating '_react2.proptypes.string')&lt;/p&gt;&lt;p&gt;The expo app has this error, what might be the problem&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Timothy</dc:creator><pubDate>Wed, 28 Mar 2018 06:12:29 -0000</pubDate></item><item><title>Re: React-Native Pin Entry View with the Native Keyboard</title><link>http://johncblandii.com/2017/05/react-native-pin-entry-view-with-the-native-keyboard.html#comment-3776412677</link><description>&lt;p&gt;Link me to the code.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">John C. Bland II</dc:creator><pubDate>Sun, 25 Feb 2018 23:48:25 -0000</pubDate></item><item><title>Re: React-Native Pin Entry View with the Native Keyboard</title><link>http://johncblandii.com/2017/05/react-native-pin-entry-view-with-the-native-keyboard.html#comment-3772414645</link><description>&lt;p&gt;its not working for me..&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nandhini</dc:creator><pubDate>Fri, 23 Feb 2018 08:57:58 -0000</pubDate></item><item><title>Re: React-Native Pin Entry View with the Native Keyboard</title><link>http://johncblandii.com/2017/05/react-native-pin-entry-view-with-the-native-keyboard.html#comment-3772401321</link><description>&lt;p&gt;I am facing some issue.. using string refs are depricated right . Suggest me some ither alternative&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">nandhini</dc:creator><pubDate>Fri, 23 Feb 2018 08:47:42 -0000</pubDate></item><item><title>Re: React-Native Pin Entry View with the Native Keyboard</title><link>http://johncblandii.com/2017/05/react-native-pin-entry-view-with-the-native-keyboard.html#comment-3762534531</link><description>&lt;p&gt;Hey, whatever works. Glad you got it going.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">John C. Bland II</dc:creator><pubDate>Sat, 17 Feb 2018 01:05:47 -0000</pubDate></item><item><title>Re: React-Native Pin Entry View with the Native Keyboard</title><link>http://johncblandii.com/2017/05/react-native-pin-entry-view-with-the-native-keyboard.html#comment-3757060667</link><description>&lt;p&gt;I tried `touchablewithoutfeedback` and `onpress`, it was causing problems with touches, So I changed it to `TouchableOpacity`` and `onPressOut`. So for me this combo worked, and if anyone is having same prob this the other option&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Raheel Hasan</dc:creator><pubDate>Tue, 13 Feb 2018 20:54:54 -0000</pubDate></item><item><title>Re: React-Native Pin Entry View with the Native Keyboard</title><link>http://johncblandii.com/2017/05/react-native-pin-entry-view-with-the-native-keyboard.html#comment-3755571512</link><description>&lt;p&gt;This is old. At the time, it was still within React. :)&lt;/p&gt;&lt;p&gt;Also, definitely define your props. It isn't just for you, but also for the compiler to solidify code expectations. You can use them with Flow, etc to better type your code.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">John C. Bland II</dc:creator><pubDate>Mon, 12 Feb 2018 23:24:09 -0000</pubDate></item><item><title>Re: React-Native Pin Entry View with the Native Keyboard</title><link>http://johncblandii.com/2017/05/react-native-pin-entry-view-with-the-native-keyboard.html#comment-3755570411</link><description>&lt;p&gt;Why set it to one as opposed to using the touchable without feedback, @Raheel Hasan?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">John C. Bland II</dc:creator><pubDate>Mon, 12 Feb 2018 23:22:45 -0000</pubDate></item><item><title>Re: React-Native Pin Entry View with the Native Keyboard</title><link>http://johncblandii.com/2017/05/react-native-pin-entry-view-with-the-native-keyboard.html#comment-3755445878</link><description>&lt;p&gt;Also, I think `propTypes` use is not really needed here. instead you can just use a constructor:&lt;br&gt;```&lt;br&gt;constructor(props){&lt;br&gt;super(props);&lt;br&gt;this.props.pinLength = 4;&lt;br&gt;this.props.pinValueLength = 0;&lt;br&gt;}&lt;/p&gt;&lt;p&gt;```&lt;br&gt;Furthermore, `React.PropTypes` is no longer valid anymore, you have to use `proto-types` &lt;br&gt;&lt;a href="https://reactjs.org/docs/typechecking-with-proptypes.html" rel="nofollow noopener" target="_blank" title="https://reactjs.org/docs/typechecking-with-proptypes.html"&gt;https://reactjs.org/docs/ty...&lt;/a&gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Raheel Hasan</dc:creator><pubDate>Mon, 12 Feb 2018 21:16:22 -0000</pubDate></item><item><title>Re: React-Native Pin Entry View with the Native Keyboard</title><link>http://johncblandii.com/2017/05/react-native-pin-entry-view-with-the-native-keyboard.html#comment-3755440364</link><description>&lt;p&gt;love the addition you made. moreover, if you do this instead its even better:&lt;br&gt;use `TouchableOpacity`` and `onPressOut`&lt;/p&gt;&lt;p&gt;&amp;lt;touchableopacity activeopacity="{1.0}" onpressout="{()="&amp;gt;{this.props.onPressPinBox()}}&amp;gt;&lt;br&gt;.&lt;br&gt;.&lt;br&gt;.&lt;br&gt;.&lt;br&gt;&amp;lt;/touchableopacity&amp;gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Raheel Hasan</dc:creator><pubDate>Mon, 12 Feb 2018 21:11:13 -0000</pubDate></item><item><title>Re: React-Native Pin Entry View with the Native Keyboard</title><link>http://johncblandii.com/2017/05/react-native-pin-entry-view-with-the-native-keyboard.html#comment-3661783584</link><description>&lt;p&gt;I'm sure they'll help someone. Thx for engaging.&lt;/p&gt;&lt;p&gt;Oh and no prob on the example. It was a fun project.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">John C. Bland II</dc:creator><pubDate>Thu, 14 Dec 2017 03:29:21 -0000</pubDate></item><item><title>Re: React-Native Pin Entry View with the Native Keyboard</title><link>http://johncblandii.com/2017/05/react-native-pin-entry-view-with-the-native-keyboard.html#comment-3660551324</link><description>&lt;p&gt;Hi, thanks for a good example! Very useful, really.&lt;/p&gt;&lt;p&gt;Simple tweaks:&lt;br&gt;1) To make TextField "real" PIN input set secureTextEntry={true} property - then you'll be able to type in numbers only (no colons and so on)&lt;br&gt;2) To be able to open keyboard again you have to surround a View in PinBoxList with &amp;lt;touchablewithoutfeedback onpress="{()" ==""&amp;gt; {this.props.onPressPinBox()}}&amp;gt;&amp;lt;/touchablewithoutfeedback&amp;gt; and add onPressPinBox={() =&amp;gt; {this.refs.pinInput.focus()}} to PinBoxList usage in your App component. Of course TextInput for a PIN have to have ref='pinInput' property.&lt;/p&gt;&lt;p&gt;I hope that someone would find that tips useful :)&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dawid</dc:creator><pubDate>Wed, 13 Dec 2017 10:50:10 -0000</pubDate></item><item><title>Re: Google Play Developer Console &amp;#8211; Alpha Testing</title><link>http://johncblandii.com/2013/05/google-play-developer-console-alpha-testing.html#comment-2328505395</link><description>&lt;p&gt;Message me. This thread isn't the place.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">John C. Bland II</dc:creator><pubDate>Mon, 26 Oct 2015 22:33:20 -0000</pubDate></item><item><title>Re: Google Play Developer Console &amp;#8211; Alpha Testing</title><link>http://johncblandii.com/2013/05/google-play-developer-console-alpha-testing.html#comment-2327870796</link><description>&lt;p&gt;hi , i need some help , if my application uploaded on google play store and i want  to upload my same application on other third party stores , what kind of changes needed my application thanks. rply&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">khawar ali</dc:creator><pubDate>Mon, 26 Oct 2015 15:04:20 -0000</pubDate></item><item><title>Re: ColdFusion 8 Ajax UI Controls: Refresh active tab???????</title><link>https://johncblandii.com/2008/03/coldfusion-8-ajax-ui-controls-refresh-active-tab.html#comment-2108365992</link><description>&lt;p&gt;coldfusion.navigate is what you need for this.  The functioh above doesn't work&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Fred</dc:creator><pubDate>Tue, 30 Jun 2015 08:18:41 -0000</pubDate></item><item><title>Re: LG G4</title><link>http://johncblandii.com/2015/05/lg-g4.html#comment-2012049435</link><description>&lt;p&gt;I've got the G2, and I've loved it for a couple years now. I was thinking of shifting manufacturers, but nobody puts out stuff better than LG. I want to wait to see how it rates, but I'll probably get it.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Nathan Strutz</dc:creator><pubDate>Thu, 07 May 2015 15:50:16 -0000</pubDate></item><item><title>Re: CFWheels: Redirecting non-authorized access after login</title><link>http://johncblandii.com/2010/08/cfwheels-redirecting-non-authorized-access-after-login.html#comment-1897453901</link><description>&lt;p&gt;Cool beans.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">John C. Bland II</dc:creator><pubDate>Mon, 09 Mar 2015 15:51:01 -0000</pubDate></item><item><title>Re: CFWheels: Redirecting non-authorized access after login</title><link>http://johncblandii.com/2010/08/cfwheels-redirecting-non-authorized-access-after-login.html#comment-1897445897</link><description>&lt;p&gt;ugh. whatever. it wraps " around the cgi.query_string for whatever reason&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike</dc:creator><pubDate>Mon, 09 Mar 2015 15:47:27 -0000</pubDate></item><item><title>Re: CFWheels: Redirecting non-authorized access after login</title><link>http://johncblandii.com/2010/08/cfwheels-redirecting-non-authorized-access-after-login.html#comment-1897444776</link><description>&lt;p&gt;&amp;lt;cfset params.params="cgi.query_string"&amp;gt;&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike</dc:creator><pubDate>Mon, 09 Mar 2015 15:46:51 -0000</pubDate></item><item><title>Re: CFWheels: Redirecting non-authorized access after login</title><link>http://johncblandii.com/2010/08/cfwheels-redirecting-non-authorized-access-after-login.html#comment-1897443313</link><description>&lt;p&gt;This doesn't take into account any additional params in the url.  Adding &amp;lt;cfset params.params="cgi.query_string"&amp;gt; before you pass it over to the session seems to do the trick&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mike</dc:creator><pubDate>Mon, 09 Mar 2015 15:46:06 -0000</pubDate></item><item><title>Re: Google Play Developer Console &amp;#8211; Alpha Testing</title><link>http://johncblandii.com/2013/05/google-play-developer-console-alpha-testing.html#comment-1888743348</link><description>&lt;p&gt;I got the answer - new apk was uploaded to alpha channel at 14 o'clock and it was updated automatically next day at 7 o'clock (about half a day delay).&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Marian Paździoch</dc:creator><pubDate>Thu, 05 Mar 2015 03:08:41 -0000</pubDate></item><item><title>Re: Google Play Developer Console &amp;#8211; Alpha Testing</title><link>http://johncblandii.com/2013/05/google-play-developer-console-alpha-testing.html#comment-1888573252</link><description>&lt;p&gt;No clue man. You might ping Google on that one.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">John C. Bland II</dc:creator><pubDate>Thu, 05 Mar 2015 00:26:29 -0000</pubDate></item><item><title>Re: Google Play Developer Console &amp;#8211; Alpha Testing</title><link>http://johncblandii.com/2013/05/google-play-developer-console-alpha-testing.html#comment-1887375086</link><description>&lt;p&gt;Yes, I have - this is why I see UPDATE instead of INSTALL. But I thought I'll see "this app need to be updated" or sth like that in the notification bar.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Marian Paździoch</dc:creator><pubDate>Wed, 04 Mar 2015 13:53:54 -0000</pubDate></item><item><title>Re: Google Play Developer Console &amp;#8211; Alpha Testing</title><link>http://johncblandii.com/2013/05/google-play-developer-console-alpha-testing.html#comment-1887193640</link><description>&lt;p&gt;I seriously apologize for not responding. Play Dev console is for the Play Store. Dev Console is for other types of things like getting access keys for oauth/etc.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">John C. Bland II</dc:creator><pubDate>Wed, 04 Mar 2015 12:17:49 -0000</pubDate></item><item><title>Re: Google Play Developer Console &amp;#8211; Alpha Testing</title><link>http://johncblandii.com/2013/05/google-play-developer-console-alpha-testing.html#comment-1887191469</link><description>&lt;p&gt;I honestly don't know. Do you have the previous alpha version installed?&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">John C. Bland II</dc:creator><pubDate>Wed, 04 Mar 2015 12:16:38 -0000</pubDate></item></channel></rss>