As Ink Calendar has evolved over the years it has become a surprisingly complex app. There are different flavors of complexity and different ways to expect and handle what is going on in the app. Some of the types of complexity found in Ink Calendar:
- Date Time
- Regional and language
- File access and saving
- Settings data validation
- Memory leaks
- Broken Windows APIs
- Control formatting and layouts
- Rapid control creation
- Bad error messages
- Overly simplistic feedback
Each one of these types of issues poses their own challenges to solve and catch before Ink Calendar crashes. Solving a single bug report can take a huge amount of effort and before the work begins it can be difficult to predict the amount of effort needed.
Data from users or Microsoft AppCenter crash reports is invaluable when it comes to making progress in a timely manner. So much of bug reports however end up being “Unspecified Error” or “The error message for this failure could not be found” etc. The best thing is getting an email from a users who has an error and working with them to get it fixed!
I am the only one working on Ink Calendar, so progress is limited by my time, but I am dedicated to fixing every bug I can identify! Please reach out via email or “Contact Me” on this website. I always love hearing from users!