<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/">
	<channel>
		<title>Fixed one annoying application bug yesterday...</title>
		<link>/blogentry/196767</link>
		<atom:link href="https://www.lotterypost.com/rss/blogcomments/196767" rel="self" type="application/rss+xml" />
		<description>hypersoniq's Blog: Fixed one annoying application bug yesterday...</description>
		<dc:language>en-us</dc:language>
		<generator>Lottery Post RSS Generator</generator>
		<item>
			<title>Original Blog Entry: Fixed one annoying application bug yesterday...</title>
			<link>/blogentry/196767</link>
			<guid isPermaLink="true">/blogentry/196767</guid>
			<pubDate>Tue, 20 Jan 2026 11:50:46 GMT</pubDate>
			<dc:creator>hypersoniq</dc:creator>
			<description><![CDATA[<p>The functions work, the data is properly displayed in columns and the numbers match the stand alone script version for both classification and Markov chain follower distribution. The problem was, the first table was always blank! You could navigate back and return and the data would be there... but what a strange issue, as zero error messages were there to identify the problem.<br /><br />So I had to do some research and it turns out I was making a correct call, but to the class and not the instance! The moment I saved the change with the proper reference, the bug disappeared! I never had to consider presentation layers and UI timing (and scope) before inside of a single script. I do not know that I would have explicitly learned of that issue without having the opportunity to troubleshoot my own project.<br /><br />The downside was I did not start on graphics as planned, but the one annoying issue that was persistent since the beginning is now solved!<br /><br />I also need to make the progress bar less tall on the draw history update screen... it takes up 1/4 of the screen height... but it works. I am now at that phase where I will not accept issues that are within my power to track down and fix. Everything is still Android safe as well. Sticking to the vision!... &#x5b;&#xa0;<a href="/blogentry/196767">More</a>&#xa0;&#x5d;</p>]]></description>
			<category>Blog Entry</category>
			<category>hypersoniq</category>
			<wfw:comment>https://www.lotterypost.com/blogentry/196767</wfw:comment>
		</item>
	</channel>
</rss>

