GridView and Grid, FOVLayer and PathLayer #252
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#252
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?
7DRL finding. The requirement to size and position a Grid when it's really serving as a container of walkable/visible data, the requirement to use a single visible/walkable dataset, and the requirement to allocate the walkable/visible layers regardless of if or how they're being used, are all huge disappointments with the current API.
first, an investigation.
Then, in "complete harmony" with the
HeightMapandDiscreteMapclasses and libtcod's underlying walkable, visible datastructures - let's provide the currentGridexperience as aGridViewwith a defaultGridwith defaultvisibleandwalkablelayers. Directly instantiating aGridmeans shared map data, with multiple or no tcod map layers inside of it; multipleGridViewinstances can share the texture cache with independent camera positions.