Willy-JL
commented
1 year ago I propose to make everyone happy by having the checker test if the "Installed" field is empty when it starts checking if that game is updated, and if it is, put the current version in that field so that when and if an update IS detected, the state of the game in the UI actually displays it as such.
No. Assuming stuff is not something I'm willing to do, it would make the situation worse in my opinion.
I personally find the update popup to be sufficient in covering the issue you're describing for how I use the tool, but I do see what you are getting at.
I counter propose 2 options, which I feel like are both reasonable:
- Add a setting for
"Installed" by defaultin Manage section,, so when you add a game and first refresh it, it will be marked as installed (I mention the first refresh because before that we don't know yet the version number so its kinda hard to put it into the installed field). - Leave the "Installed" box behavior unchanged, and instead change the behavior of the "Update" marker (yellow circle star icon). Instead of mirroring 1:1 what the middle state of the "Installed" checkbox does, create a new
updatedfield (on backend) so that (frontend) any update will make the update marker visible, regarless of whether the game is marked installed or not. This then brings another question, as in how does the user hide the update marker? Of course checking the installed box again would make it go away as it does now, but it might be worth adding another button / right click action to mark the update as "acknowledged" or whatever
I feel like the latter option is the most appropriate solution, while the first is more of a workaround, but they don't exclude each other, they could be used for different purposes so I'm willing to implement both
FaceCrap
Will push and build in a sec. You know the rest ;)
Ok, I know we had this discussion in the past, and I was reluctant to bring it back up, but I feel this may be the one situation where it may (stress "may") be desirable to allow for a small change in your logic. It certainly would help with my sense of logic, as I am much like Spock here.
I know from looking at the DB that the "Installed" field is a text field that gets the current version of a game once the "Installed" checkbox is fully ticked. Which in turn triggers the checker's logic to display the "Installed" checkbox in a semi-checked state and places that black-star-on-yellow-circle icon before the game name when an update is found during a check. And as long as a user does not put a full tick in the "Installed" checkbox after it becomes semi-checked, that value will not change whenever a new update is detected.
Now, as said, I am much like Spock here in that when I add a new game to F95Checker, my sense of "logic" gets a bit bent out of shape if I have to "fake" that the game is installed by ticking the "Installed" checkbox. The more so if I don't intend to ever download that game for the time being, e.g. because I only added it to start keeping track of its update cycle. (And as side note, also labeled it as "Maybe" for the Kanban column view)
The average user will likely not know how this mechanism works, so will probably also not put a tick in that box for a new game for whatever reason, or simply forgetting to.
I propose to make everyone happy by having the checker test if the "Installed" field is empty when it starts checking if that game is updated, and if it is, put the current version in that field so that when and if an update IS detected, the state of the game in the UI actually displays it as such.
This has three benefits. A) It satisfies my sense of logic (less important) B) feels more natural for games that only get added to keep track of their update cycle C) it makes sure that an update actually shows as an update in situations where a user, who actually knows how this mechanic works, simply has forgotten to tick the "Installed" box. (ehm, like me 🙄)
Alternatively, that field could also be seeded when the game gets added, even though that feels somewhat illogical because you see this field as "reflecting if the latest update is or is not installed" and not if an update actually has been installed before. Actually, that is exactly what the semi-checked state does, it reflects your logic that the latest update is not installed, but it only shows like this when telling the checker there was a previous update installed even if it wasn't.
In other words, it prevents a PEBCAK or PICNIC situation.