- Oct 1, 2020
- 1,528
- 1,059
If you're on Windows, the scrollwheel works just fine when hovering the taglist, also much faster than dragging the scrollbar.this tiny little scrollbar really suck,
If you're on Windows, the scrollwheel works just fine when hovering the taglist, also much faster than dragging the scrollbar.this tiny little scrollbar really suck,
it still scrolling, potentially through whole listIf you're on Windows, the scrollwheel works just fine when hovering the taglist, also much faster than dragging the scrollbar.
Still better than trying to hit that little scrollbar in absence of type-ahead. Even less scrolling when freewheeling. Just one quick flick and it's at the bottom.it still scrolling, potentially through whole list
LOL, just saw that happen here too.actually, i just saw the font flicker to comic sans for a split second right in front of me...
build 11.1 beta 1603 (latest)
Every time I start the program this window appears:
View attachment 4698662
I close it and everything seems to work fine.
I cleared all cookies, just in case, but this window still appears every time I start the program.
should be fixed in latest betaOh and 1603 show no notifications, but as i read is already known due new method and dependencies?
Testing it as we speak, will edit this message once a refresh happens.should be fixed in latest beta
Was the f95checker window focused when it happened? Notifications aren't sent when focusedTesting it as we speak, will edit this message once a refresh happens.
Well, took me a while to be able to edit this message.
But there are 2 things that I can report. First being the error when you start Checker, is gone so yay. Second being that desktop notifications still don't work.
Nope, running in background in taskbar. When I opened the app from notification area, I had a game update, but no notification for it.Was the f95checker window focused when it happened? Notifications aren't sent when focused
Were you playing some video games or had an app full screened (not maximized, but full screen)?Nope, running in background in taskbar. When I opened the app from notification area, I had a game update, but no notification for it.
Nope, just watching youtube and not in full screen mode. Oh and Do not Disturb is off as well. So no full screen apps running, checker in background, running normally, DnD disabled, but no notification appears.Were you playing some video games or had an app full screened (not maximized, but full screen)?
How often are games checked nowadays after they show up in latest updates?
Sisterly lust, Matrix hearts, Lust theory have had ancient update dates for quite a while since their recent updates.
reinstall and make sure your antivirus doesnt delete files inside it.
If it was not promoted then why did the checker notify me about the latest update on SL?View attachment 4712012
the update was not "promoted" to latest updates. im tired of explaining why it is like this, and why there is no good solution.
Likely because the version number changed.If it was not promoted then why did the checker notify me about the latest update on SL?
I guess the latest updates DB is even more wack if Lust theory is shown as having the latest update in 2018.
the stuff on latest updates is based on a redis cache, which is a lot faster and lighter than going through the xenforo backend. when uploaders update a thread and the version number changes, it gets updated in the redis db that latest updates uses. this however, does not automatically trigger a "promotion". a promotion is triggered manually by uploaders, marking the date that the update happened, and this pushes it to the top of latest updates (or not, if they manually mark a date in the past, which they often do if the update was a few days ago, in which case its not at the top but higher than it was before). they dont always do this, either because the game author is abusing the system publishing tiny updates every day to stay at the top of latest updates, or by simple human error by the uploaders forgetting or typoing the date of promotion. the same way that human error couldve occurred with the old method of parsing the update date from the thread description, in which case uploaders could typo it, forget to update it, or use the wrong date format, or put a date 20 years in the future (yes, this did happen). and making the cache api record its own "update date" of when it noticed a change of version number is error prone too, because despite how many users use f95checker, even all of them combined do not track all games, and do not track them 24/7, so if a game gets an update on monday but no one that uses f95checker refreshes that game until sunday, then the new version is picked up on sunday and the updated date is wrong (or it could be several months inbetween instead of just monday to sunday, which would be more of a problem). there is no good way to solve this correctly. and so we must bear with human error. i suggest you sort your list according to the finished and installed checkboxes instead of just by the updated date, then the only risk is your human error. something like this:If it was not promoted then why did the checker notify me about the latest update on SL?
I guess the latest updates DB is even more wack if Lust theory is shown as having the latest update in 2018.
Still, i thought that every 2 weeks the cache gets updated, so funky release dates would be fixed eventually. But it seems that your caching server only interacts with latest updates, and doesn't crawl the first forum posts periodically?the stuff on latest updates is based on a redis cache, which is a lot faster and lighter than going through the xenforo backend. when uploaders update a thread and the version number changes, it gets updated in the redis db that latest updates uses. this however, does not automatically trigger a "promotion". a promotion is triggered manually by uploaders, marking the date that the update happened, and this pushes it to the top of latest updates (or not, if they manually mark a date in the past, which they often do if the update was a few days ago, in which case its not at the top but higher than it was before). they dont always do this, either because the game author is abusing the system publishing tiny updates every day to stay at the top of latest updates, or by simple human error by the uploaders forgetting or typoing the date of promotion. the same way that human error couldve occurred with the old method of parsing the update date from the thread description, in which case uploaders could typo it, forget to update it, or use the wrong date format, or put a date 20 years in the future (yes, this did happen). and making the cache api record its own "update date" of when it noticed a change of version number is error prone too, because despite how many users use f95checker, even all of them combined do not track all games, and do not track them 24/7, so if a game gets an update on monday but no one that uses f95checker refreshes that game until sunday, then the new version is picked up on sunday and the updated date is wrong (or it could be several months inbetween instead of just monday to sunday, which would be more of a problem). there is no good way to solve this correctly. and so we must bear with human error. i suggest you sort your list according to the finished and installed checkboxes instead of just by the updated date, then the only risk is your human error. something like this:
View attachment 4712329
my cache is not outdated. threads get rechecked atleast once a week, or sooner if some change is detected with the latest updates api or version api (based on the same latest updates data). the issue is that the data in latest updates is wrong, because the update was not promoted, and thus it has a older date.Still, i thought that every 2 weeks the cache gets updated, so funky release dates would be fixed eventually. But it seems that your caching server only interacts with latest updates, and doesn't crawl the first forum posts periodically?
Cant the date from the first post be used/updated/watched? Or atleast a sanity check if the update date is within 1 month of current date when version number changed.the issue is that the data in latest updates is wrong, because the update was not promoted, and thus it has a older date.