Earlier, I came across a bug related to progress bars experiencing lags whenever a user attempted to click the cancel button. As I’ve mentioned in the previous blog, I observed that GUIDs were overseeing the progress bar, causing it to increment each time a user initiated the cancel action. I suspected that the cancellation process might not be fully executed, and the accumulation of GUIDs during each cancellation could be the root cause of the lagging problem. Thankfully, Mr Peter helped and solved the GUID bug by eliminating the progress signal that triggered multiple GUIDs. As a result, the problem of the bug of the unresponsive cancel button of the progress bar was effectively resolved.
Subsequently, I made sure to clean up the code before making the final commit and push. The following day, Mr. Peter assigned me a new and interesting task. This was prompted by the software’s maturation, which allowed for the collection of extensive data with the aim of extracting more information and insights. Mr. Peter provided a general overview of the task, where the objective of this new task is to get the most value out of the data that had been made. He instructed me to conduct preliminary research.
I began my exploration on YouTube to gain a general understanding of report data and data analysis, aiming to discern the optimal outcomes. Next, I delved into researching the appropriate medium to use, debating between PowerBI and WPF. My initial inclination leans towards WPF, incorporating the widely-used LiveCharts package. This lightweight library is known for its ease of use and seamless integration into applications, particularly excelling in real-time data visualization scenarios where data is frequently updated. LiveCharts being open-source adds to its appeal, allowing for free and customizable use by developers. While PowerBI boasts a broader range of features for data visualization, business intelligence, and analytics, its learning curve may pose a challenge for new users. Further research is needed to make an informed decision.
Approaching the end of the week, a minor bug surfaced in the previously committed code. Pagination was malfunctioning, and additional progress bar implementations were deemed necessary.