[Minor Feature] Engine-level modifier key state tracking #160
Labels
No labels
Alpha Release Requirement
Bugfix
Demo Target
Documentation
Major Feature
Minor Feature
priority:tier1-active
priority:tier2-foundation
priority:tier3-future
priority:tier4-deferred
Refactoring & Cleanup
system:animation
system:documentation
system:grid
system:input
system:performance
system:procgen
system:python-binding
system:rendering
system:ui-hierarchy
Tiny Feature
workflow:blocked
workflow:needs-benchmark
workflow:needs-documentation
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
john/McRogueFace#160
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Summary
Currently, detecting modifier key combinations (like Shift+Tab, Ctrl+S) requires Python code to manually track modifier state by processing press/release events. This is error-prone and duplicates effort across projects.
Proposed Solution
Add engine-level tracking of modifier key state, exposed to Python via:
Benefits
Implementation Notes
SFML provides
sf::Keyboard::isKeyPressed()which can query modifier state at any time. This could be exposed directly or used to populate a modifiers dict passed to handlers.Workaround
Until implemented, Python code can track modifiers manually:
Related