Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Blitter loops on partially-transparent frames leave cruft #1093

Closed
dankamongmen opened this issue Nov 1, 2020 · 3 comments
Closed

Blitter loops on partially-transparent frames leave cruft #1093

dankamongmen opened this issue Nov 1, 2020 · 3 comments
Assignees
@dankamongmen
Milestone
2.1.0

Comments

@dankamongmen
Copy link
Owner

I'm not certain of our sex_trans_check() in its entirety. Do a unit test to verify the glyph output for each of 64 transparency bitstrings. I think we ought do this before we release sexblitter in 2.0.3.
@dankamongmen dankamongmen added this to the 2.1.0 milestone Nov 1, 2020
@dankamongmen dankamongmen self-assigned this Nov 1, 2020
@dankamongmen
Copy link
Owner Author

yeah this can't be right, and doesn't seem a manifestation of #1068

2020-11-01-093337_136x217_scrot

@dankamongmen dankamongmen changed the title close-in unit tests for sexblitter Blitter loops on partially-transparent frames leave cruft Nov 1, 2020
@dankamongmen
Copy link
Owner Author

i think this is actually residue from the prior frame in the walk cycle, yeah, fixed.

dankamongmen added a commit that referenced this issue Nov 1, 2020
@dankamongmen
ncvisual_stream: erase before each draw for partial transparencies #1093
20ff1fe
@dankamongmen
Copy link
Owner Author

yep, works perfectly now

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dankamongmen dankamongmen

Labels
None yet
Projects
None yet
Milestone
2.1.0
Development

No branches or pull requests
1 participant
@dankamongmen