How Seatify recognises a Winamax window
Winamax is one of the few rooms Seatify matches on the window title alone. Most rooms require the title AND the window class name to agree before a window is accepted as a table; the Winamax definition carries no class requirement at all.
That is a practical advantage rather than a technical footnote. Window class names change when a client is rebuilt — a new framework version, a new renderer — and a manager that keys off the class stops seeing your tables the morning after an update. Matching on the title means a Winamax update has to rename the windows themselves to break detection, which is far rarer.
- Matched by
- Window title containing “Winamax”, case-insensitive
- Class name required
- None — any class is accepted
- Survives client updates
- Yes, unless window titles change
Tables, lobby and rail told apart
A tiling layout is only useful if the lobby does not land in a table slot. Seatify classifies every Winamax window before placing it, using the markers in its room definition: the lobby and cashier windows are recognised as lobby, hand replayer windows as replayer, and observed tables as spectator.
The spectator markers include the French forms your client actually produces — “(spectateur)” alongside “(watching)” — because a Winamax client in French labels a railed table that way. A table you are watching therefore goes to your spectator slot instead of taking a seat slot from a table you are playing.
- Lobby
- Titles containing lobby, cashier, tournament lobby, my tournaments, deposit, withdraw
- Replayer
- replayer, replay, hand history, historique, rejoueur
- Railing
- (spectateur), (watching), observer, rail
Winamax next to everything else
Seatify does not stop at poker windows. App slots hold whatever else belongs in your session — Discord, a browser, your tracker, a spreadsheet — in fixed positions alongside the tables, so a Winamax session opens the same way every time without you arranging six windows first.
If you play Winamax and a second room together, both sets of tables go into the same layout. Detection is per-window, not per-application, so a mixed session is not a special case.
When the client updates: Seatify Engine
Every detection rule above describes how the client behaves today. Rooms change their windows without notice, and historically that meant a broken layout until our next release.
Seatify Engine removes that wait. When a window stops being recognised, you open the Table Manager, point at it, and say what it is — a table, a lobby, a waiting room, a replayer or a railed table. The rule is saved on your machine and applies immediately.
You can then share it with one click. Once reviewed, it joins the set every installation can fetch, so the first player to hit a change fixes it for everyone. Downloaded rules are cryptographically signed and verified before being applied, and your own rules always outrank them. A shared rule carries the shape of a window title and nothing else: no tournament numbers, no stakes, no player names. It is available during the free trial too.
How it runs on your machine
Seatify Pro reads the properties Windows already exposes for every open window — its title, its class name, its size and position — and moves windows using the same Windows APIs any window manager uses. It never attaches to the poker client, never reads its memory, and never touches the cards or the action.
That boundary is deliberate and it is what keeps the tool inside room rules. A table manager that injected into the client would be both a security risk and a banning risk, and no amount of convenience is worth either.
