Seizer solitaire

Built using seizer and implementing the same addictive variant of solitaire found in Last Call BBS; seizer solitaire gives you a way to pass the time on any x86_64 or aarch64 machine that has a Wayland compositor.

You can even run it on little gaming handhelds running ROCKNIX:


To run on a ROCKNIX device you’ll want to put the aarch64-linux-none build in roms/ports, and then (so emulation station will pick it up) add seizer-solitaire.sh to the same folder:

#!/bin/sh
/storage/games-internal/roms/ports/seizer-solitaire
14 Likes

This is sweet!

By the way it runs at 100% CPU for me - not sure if you’re aware of that. I’ll file an issue if you like.

I suspect you’re running into performance issues with the multi-threaded rendering I recently added, but I don’t have a tracking issue for that anyway. What (physical) resolution are you running it at?

If it is the multi-threaded rendering you’re running into, then I need to do one or more of the following to fix it:

  1. Profile the multi-threaded renderer and optimize hot spots
  2. Render at a lower resolution and let the compositor upscale it (the assets aren’t high resolution anyway)
  3. Implement a different rendering backend that relies more heavily on the compositor using the subcompositor protocol

So uh, feel free to open an issue, or I’ll make one later.

1 Like

I didn’t resize the window:

btw it crashed when I pressed the print screen button!

It doesn’t seem slow, are you sure it’s not a vsync issue? Maybe it’s rendering frames at an unlimited speed with no sleep()?

Oh! Never mind, the backtrace made me see the issue actually.

It’s this kde bug which will be fixed with the next update.

1 Like

Ah, okay. I’ll have to fix that bug with print screen, but I’ll hold off on doing performance optimization. Thanks for the follow up!

New release! See the link for details.

1 Like

What Zig version is the project using?

Its being built on the pipeline using 0.12.0

Sorry, that script is outdated ( I do need to get CI set up at some point). I mentioned it in a issue here, version 0.14.0-dev.3188+34644511b, with plans to target 0.14.0 stable when it releases.

New release!

[0.3.0] - 2025-02-21

Changed

  • Menus have had a visual overhaul, with image assets provided by @desttinghim!
    • The black background for menus has been replaced with a panel image
    • Buttons now have a background image resembling a key cap
  • How a “hovered” button is indicated has changed:
    • “Hovered” button is no longer surround with > and < characters
    • When moving with gamepad/arrow keys, a cursor is rendered on the currently “hovered” button.
    • The currently hovered button is rendered using an “anticipation frame”.
  • The swap_confirm_and_cancel setting now uses a radio button to select the value

Added

  • Menus now support mouse input.
  • A radio button component has been added. Again, the image assets were created by
    @desttinghim, and they sport a blocky design more inspired by buttons on cassette
    player than the circular buttons used in most GUIs.
  • The About menu now has set of radio buttons to indicate which page is selected.

Fixed

  • Cursor holding cards no longer flickers when moving over stacks
  • When using double click to move cards to the foundation from the drawn cards pile,
    the cursor will now be correctly placed on the last card in the pile, instead of
    at the top of a movable stack.

Screenshots

6 Likes