Tinos3 and the Great Issue Wars

Hi! We're taking a look back at October and the issues Tinos3 has encountered along the way. These issues have ranged from relatively easy fixes to problems that are outside my control.

There have been a LOT of bugs in Tinos3 this month. However, since we rewrote the environment and the entire codebase, we've also managed to eliminate a few issues from the old, legacy codebase. This post will focus exclusively on issues encountered after the rewrite.

Lua

When Lua was introduced during the rewrite, we encountered an issue where Lua wouldn't recognize a custom-registered Lua function. This eventually resulted in a .NET exception when the function returned a nil value.

It was one of the issues we had to investigate while getting Lua integration working properly in the rewritten codebase.

Formatting and partitioning

More recently, we encountered a bug in the FDisk utility that prevented it from formatting a partition unless the disk had already been mounted.

This created a bit of a catch-22: the utility needed to mount the partition before formatting it, but the partition couldn't be mounted because it didn't have a filesystem yet.

Fortunately, this issue has now been fixed!

Graphics, resources, and the mouse

As development of the desktop environment and window system continues, we've encountered an issue where the mouse cursor doesn't change position. This issue remains unresolved as of writing this post.

We also ran into a few issues involving the mouse cursor's resources, but those have since been fixed. These fixes weren't a major part of the development commits, so they were easy to overlook among the other changes.

What's next?

Development continues, and so does the debugging. With Tinos3 0.2 still a way off, there's plenty of work left to do as we improve the desktop experience and resolve the remaining issues. Our goal is to release Tinos3 0.2 by the end of 2027.

More updates will follow as development progresses!