Quote: "So how do TGC decide what features to implement?"
i don't know the answer to that as i'm sure there's plenty to it that i have no knowledge of. business decisions, $$, time, etc., and how difficult the fixes or features might be to implement, etc, (and, again, i'm sure there are more facets that i don't know about - maybe "how many users would it help?" is in there, too?).
what i do know is that i was asked to help label the github issues in early june i think it was, in preparation for future Updates where the labels hadn't been added for some time. i
labelled everything going back to late beta (2019). some i was able to close as being fixed but not removed from the queue. some were duplicates, and some turned out to not be bugs (i spent a lot of time testing what i could, etc, beyond the labelling).
otherwise, High Priority was added to basically "crippling" issue where commands or functionality was broken. everything was also labelled by platform/OS, whether it was a core, studio IDE, export issue, etc.. i asked for additional labels such as Help/Document issues (all of which were provided to me) and tried to organize it all as best i could.
and, i know that what i did on the gihub issues is not all that was done there where rick and others swept through it, added to it, etc, leading up to beginning on this Update.
around that time, i was asked for a top 10 list of what i considered "crucial" based on observation of the forums, etc.. i provided a somewhat shorter list while pointing to the 18 (at the time) "high priority" issues on the github and some of that was addressed (there are 11, now, including yesterday's "failed to check for java").
frankly, this update has a lot more than i expected to be included such as some studio IDE issues that preben had time to sneak in and general "quality of life" work like .IndexOf() and documentation additions like filename case sensitivity and .byc reference/clarification. i truly expected android export work and a "few" other things so i'm pleasantly surprised. alas, that exposes how little i do know about what TGC has on their mind or makes decisions.
i know that a couple/few years ago, rick posted a poll. i don't recall how that translated into what was addressed and what wasn't. i know that none of what i voted for was implemented but, i've got my biases. IE, i use AppGameKit as a hobby, and i dont use a lot of the command sets, while its a source of income for others.
i considered posting a similar poll a couple of months ago but i couldn't think of how to make it "secure" without requiring email addresses (and then validating/confirming them?). what i was afraid of is someone(s) spamming the poll with THEIR wish list leaving the results worthless as an indicator of what we want to see AS A WHOLE.
some have suggested Up-voting on the github. i don't know how accurate that would be where a lot of us don't use github, but i expect it couldn't hurt.
that's about all i know except that i was enlisted to help TGC help US
. i've received their support and their attention when necessary which, for me, says something about their dedication to US
. and, that's why i continue doing "what i do" to that end.