Krzysztof kuhy Rudnicki
c963cd88a8
Phase 2 of the shared-component work. gatelock owned the tokens but stopped short of composite widgets, so four gate apps each built the same ones and drifted apart doing it. widgets.py: - make_button(), from diet-guard's _gatelock_buttons. Emphasis is a variant, not a colour pair, so the text colour is picked *from* the fill and a call site structurally cannot produce the fg-vs-on_fill contrast bug. Binds <Return>/<KP_Enter>, which Tk does not give tk.Button on X11, and takes its focus ring from LockConfig (Tk's default 1px black is invisible on #211D1B). - heading() and row(), from leetcode-guard's _status_sections. row()'s wrap width is a parameter rather than the donor's module-level dict, which made every row's wrapping depend on whichever window rendered most recently. widget_group.py: - WidgetGroup, replacing ~916 lines of per-output fan-out across four repos. Takes the union of what they needed and the fixes only some of them had: first -> W|None (three donors could IndexError on zero outputs), TclError suppressed per copy (one donor did not guard at all), focus deliberately singular rather than fanned out, and kwargs typed `object` so command= is expressible. Stores (output_name, widget) pairs, which designs out a latent strict-zip ValueError in the donor that kept two parallel lists. Additive only: nothing is removed from the consumers in this commit, so all four gates keep working on their current pin. 100% branch coverage, real-Tk tests under xvfb. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01C1qGVUMjmtppci6Fjxs9xS |
||
|---|---|---|
| .. | ||
| gatelock | ||
| .pre-commit-config.yaml | ||
| LICENSE | ||
| pyproject.toml | ||
| README.md | ||
| requirements.txt | ||
gatelock
Shared fullscreen lock-window + HMAC log-integrity backend, extracted from three personal automation tools that each independently implemented "lock the screen with a blocking overlay until a condition is met": diet_guard, wake_alarm, and screen-locker.
Why
All three reimplemented the same tkinter fullscreen mechanics (overrideredirect,
input grab, VT-switch disable) at different levels of maturity, and the
HMAC-signed-state module had already been hand-copied between two of them
because they live in separate repos. gatelock is the one place that logic
now lives.
Install
pip install "gatelock @ git+https://github.com/kuhyx/utils@gatelock-v0.1.1#subdirectory=gatelock"
Usage
import tkinter as tk
from gatelock import GateRoot, LockConfig, LockWindow
class MyGate:
def __init__(self, *, demo_mode: bool) -> None:
self.root = GateRoot()
self.root.on_callback_error = self._handle_callback_error
config = LockConfig(mode="soft" if demo_mode else "hard")
self._lock = LockWindow(self.root, config, hooks=self)
self._lock.setup()
# ... build your widgets ...
self._lock.grab_input()
def on_focus_ready(self) -> None:
self.my_entry.focus_force()
def on_callback_error(self) -> None:
self.close()
def on_close(self) -> None:
... # release any hardware/state held while locked
def close(self) -> None:
self._lock.close()
def run(self) -> None:
self._lock.run()
LockConfig's mode preset bundles the common combination ("soft" = topmost
only, typeable, WM-escapable; "hard" = overrideredirect + global grab +
VT-disable). Each axis (overrideredirect, grab, disable_vt,
grab_retry_ms) can be set explicitly to reproduce a consumer's exact prior
behavior where it diverges from the preset.
gatelock.log_integrity ports the HMAC-signed state module used by all three
projects; DEFAULT_HMAC_KEY_FILE (/etc/workout-locker/hmac.key) is
unchanged so existing signed history keeps verifying.
Development
python -m venv .venv && source .venv/bin/activate
pip install -r requirements.txt
pytest
pre-commit install && pre-commit install --hook-type pre-push