feature request applied:
Auto-follow now pauses as soon as you scroll away from the live edge: entries keep piling up in the background, but the view stays exactly where you left it. Following resumes on its own once you're back at the newest entry. While it's paused, a small bar shows how many entries arrived in the meantime and takes you back to the live edge in one tap.
The game chat and the lobby chat had the mirror-image problem (every message forced the view back to the bottom) and now behave the same way.
already up and running ( build 2.1.4-web.116)
PokerTH Web Client
-
Spitessbir
- Posts: 25
- Joined: Fri Mar 29, 2024 1:09 pm
1. The log auto scroll pause works for a while but later in the game it stops working. It has happened twice to me. I can't discover what triggers this behaviour.
2, Perhaps you missed my earlier post about this, but the tooltip text for the globe translate icon is still in French despite the English language setting.
2, Perhaps you missed my earlier post about this, but the tooltip text for the globe translate icon is still in French despite the English language setting.
Both fixed in build 2.1.4-web.119, thanks.
1. The log is capped at 500 entries; past that, the pause logic lost track of your position and the view crept down. It now anchors on the line you're reading.
2. You were right, and it wasn't only the globe — I swept the whole client and found about fifteen more labels stuck in French. All translated now.
1. The log is capped at 500 entries; past that, the pause logic lost track of your position and the view crept down. It now anchors on the line you're reading.
2. You were right, and it wasn't only the globe — I swept the whole client and found about fifteen more labels stuck in French. All translated now.
-
Spitessbir
- Posts: 25
- Joined: Fri Mar 29, 2024 1:09 pm
I want to make some suggestions for consistency across all the clients.
1. Currently you can make a bet ahead of time (before your turn) using the mouse to click on one of the 4 action buttons. (Fold/Check/Bet/Raise/All-in). But you should also be able to do this with the F1/F2/F3/F4 keys as you can with the other clients but is currently not possible.
2. After you fold, you can still click and activate any of the 4 action buttons with your mouse. This should not be possible. That area should be a dead zone after you have folded.
1. Currently you can make a bet ahead of time (before your turn) using the mouse to click on one of the 4 action buttons. (Fold/Check/Bet/Raise/All-in). But you should also be able to do this with the F1/F2/F3/F4 keys as you can with the other clients but is currently not possible.
2. After you fold, you can still click and activate any of the 4 action buttons with your mouse. This should not be possible. That area should be a dead zone after you have folded.
Thanks — both were right, both are in (build 2.1.4-web.124).
1. F1–F4 now arm a pre-selection off turn, same as clicking. Press again to disarm.
2. Dead zone added, and it goes wider than folding: the buttons also stay off when all-in, at showdown, while the board is dealt, and after you have acted until someone actually re-raises. That is what the widget and QML clients do, so that is what I matched.
We're all aiming for all clients to behave the same, and the web one follows the others rather than going its own way. A few differences will probably stay — the widget client's flow is well established and players rely on it — but do keep pointing them out, we look at each one.
1. F1–F4 now arm a pre-selection off turn, same as clicking. Press again to disarm.
2. Dead zone added, and it goes wider than folding: the buttons also stay off when all-in, at showdown, while the board is dealt, and after you have acted until someone actually re-raises. That is what the widget and QML clients do, so that is what I matched.
We're all aiming for all clients to behave the same, and the web one follows the others rather than going its own way. A few differences will probably stay — the widget client's flow is well established and players rely on it — but do keep pointing them out, we look at each one.
-
Spitessbir
- Posts: 25
- Joined: Fri Mar 29, 2024 1:09 pm
The web client can become sluggish with a large amount of log files stored so it's probably a good idea to place some kind of a limit on how many you keep. You already have an option for storing logs 'Forever' and then for up to 90 days but I suggest you have more options, say up to 365 days.
EDIT: I'm assuming you are going by the log date and not the import date for logs that were imported when deciding how long to keep logs.
EDIT: I'm assuming you are going by the log date and not the import date for logs that were imported when deciding how long to keep logs.
Good call, thanks.
Retention now offers 7 / 30 / 90 / 180 / 365 days, plus a second setting capping how many logs are kept (20 / 50 / 100 / 200).
And yes — it goes by the log's own date, read from the .pdb, never the import date.
Imported logs are now exempt from auto-deletion entirely, so nothing you bring in from the desktop client disappears on you.
The Logs window also got faster: it no longer loads every stored hand just to show the list.
Retention now offers 7 / 30 / 90 / 180 / 365 days, plus a second setting capping how many logs are kept (20 / 50 / 100 / 200).
And yes — it goes by the log's own date, read from the .pdb, never the import date.
Imported logs are now exempt from auto-deletion entirely, so nothing you bring in from the desktop client disappears on you.
The Logs window also got faster: it no longer loads every stored hand just to show the list.
-
Spitessbir
- Posts: 25
- Joined: Fri Mar 29, 2024 1:09 pm
I would also like to suggest a more aggressive fading of avatars and cards of players that have folded. Currently it isn't always obvious to me how many players are still active in the hand.
-
Spitessbir
- Posts: 25
- Joined: Fri Mar 29, 2024 1:09 pm
Thanks. That looks much better.
I think I must stop now until I find a real bug.
