v2.0.0 Status Update #6
DarkDevRBLX
announced in
Announcements
Replies: 1 comment
|
Due to some personal issues around the time I began working on v2.0.0 again after this post, I was unable to meet the deadline. Apologies, DarkDevRBLX. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello everyone!
As v1.5.0 reaches the 1-year-ago upload mark, I'd like to give everyone an update on v2.0.0.
I would like to confirm that for the most part, v2.0.0 is complete!
If you don't want a teaser to upcoming features I recommend you skip to the end.
While I won't spoil all of the features that are coming, one feature in particular has been problematic. This feature is also one that has been in TextPYOS since v1.0, so what could it possibly be?
The feature in question is the directory. But how could the directory cause problems? Well the directory itself is not the problem, but rather how I've chosen to recode it.
My goal with the directory recode was to have it check a list and if your input was in that list, it would run a check to see which function/feature you were requesting the function for. Simple, right? Yes.
But the problem with this is that I ended up spending several months trying to get it to work with little success. Granted most that time was spent doing hobbies outside of TextPYOS, but whenever I would try to work on TextPYOS, I looked at the code once and closed my editor.
I've set myself a deadline to get TextPYOS completed, tested, and working by the end of March (2026). Mostly for the fact that I wanted v2.0.0 done no more than 2 months after v1.5.0 was published, but that never happened.
Essentially to recap since I went on a tangent, TextPYOS v2.0.0 has been overshadowed by other projects I'm working on, and the directory recode is causing me problems, but TextPYOS is still in the works.
-DarkDevRBLX
All reactions