froxxxy/bscscore
1
0
Fork 0
Code Issues 2 Pull Requests Actions Packages Projects Releases Wiki Activity

Winnerbreak / Wechselbreak #28

New Issue
Closed
opened 2025-10-30 11:15:25 +01:00 by froxxxy · 2 comments
froxxxy commented 2025-10-30 11:15:25 +01:00
Owner
Copy Link

On game creation there shall be another option:

Winnerbreak / Wechselbreak

  • Make it a new screen in Game Creation

  • User has to pick one of them, With Winnerbreak being default

  • On Next Screen User has to pick which Player will break first

  • If Wechselbreak and 3 Players: User also has to pick which Player will break second

  • On Game Detail View the breaking player will be shown by a small white filled circle next to his score

  • After each input recalculate which Player is breaking:
    -- Winnerbreak: Player who won last game will also break the next one
    -- Wechselbreak: Players alternate breaks. On Three Players keep the order chosen on game creation

Develop this in a separate git branch.

On game creation there shall be another option: Winnerbreak / Wechselbreak - Make it a new screen in Game Creation - User has to pick one of them, With Winnerbreak being default - On Next Screen User has to pick which Player will break first - If Wechselbreak and 3 Players: User also has to pick which Player will break second - On Game Detail View the breaking player will be shown by a small white filled circle next to his score - After each input recalculate which Player is breaking: -- Winnerbreak: Player who won last game will also break the next one -- Wechselbreak: Players alternate breaks. On Three Players keep the order chosen on game creation Develop this in a separate git branch.
cursor commented 2025-10-30 14:08:06 +01:00
Collaborator
Copy Link

Merged feature branch into main.

  • Merge commit: 6da7a5f4e2
  • Branch: feature/winnerbreak-wechselbreak-#28 → main
  • Highlights:
    • New break rule and order steps with persistence of last-used values
    • Auto-advance behaviors adjusted; arrow navigation consistent across steps
    • Breaker indicator inline by name; -1 acts as undo; rotation logic per spec

If you want this issue closed now, I can update the state to closed.

Merged feature branch into main. - Merge commit: 6da7a5f4e2c83ae0d31b26be62898e9b775c963b - Branch: feature/winnerbreak-wechselbreak-#28 → main - Highlights: - New break rule and order steps with persistence of last-used values - Auto-advance behaviors adjusted; arrow navigation consistent across steps - Breaker indicator inline by name; -1 acts as undo; rotation logic per spec If you want this issue closed now, I can update the state to closed.
cursor commented 2025-10-30 14:34:13 +01:00
Collaborator
Copy Link

Committed UX improvements to new game wizard.

  • Disable right-arrow on Player1/2 until name entered
  • Disable right-arrow on Player3 unless name entered (skip still available)
  • Disable right-arrow on Race To until value present
  • Break type: no preselect; disable next until rule chosen
  • First break: no preselect; disable next until required choices

Commit: 26a97e7

Refs #28

Committed UX improvements to new game wizard. - Disable right-arrow on Player1/2 until name entered - Disable right-arrow on Player3 unless name entered (skip still available) - Disable right-arrow on Race To until value present - Break type: no preselect; disable next until rule chosen - First break: no preselect; disable next until required choices Commit: [`26a97e7`](https://gitea.schwenk.online/froxxxy/bscscore/commit/26a97e7eaaba95112573e1cd47e0466c2d0e825b) Refs #28
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
cursor froxxxy
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: froxxxy/bscscore#28
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?