Skip to content

Conversation

@allkern
Copy link
Member

@allkern allkern commented Apr 25, 2021

I'm not exactly sure on where to put this information in, so I just dropped it here, It would be good to describe an example too, maybe also a little diagram explaining it? I can do that if you want me to, but I decided to just keep it like this until I get some more info about PRs on this doc (such as keeping the design language of diagrams consistent).

I'm not exactly sure on where to put this information in, so I just dropped it here, It would be good to describe an example too, maybe also a little diagram explaining it? I can do that if you want me to, but I decided to just keep it like this until I get some more info about PRs on this doc (such as keeping the design language of diagrams consistent).
@ISSOtm
Copy link
Member

ISSOtm commented Apr 26, 2021

This section is more of a beginner-friendly overview, and not really the right place to get into nitty-gritty details. The other place where weird window behavior is described is the WX/WY registers, so maybe add an info bubble there?

@allkern
Copy link
Member Author

allkern commented Apr 26, 2021

Yep, I just moved it to the bottom of WY's description, but I still feel this is not its place, as it is not directly related with WY anyways. I'm thinking here might be better?

@ISSOtm
Copy link
Member

ISSOtm commented Apr 26, 2021

Right, yeah, I think that makes sense.

@allkern
Copy link
Member Author

allkern commented Apr 26, 2021

There you go, I moved it and made it into an info bubble

@allkern
Copy link
Member Author

allkern commented Apr 26, 2021

Done!

@ISSOtm
Copy link
Member

ISSOtm commented Apr 26, 2021

Are there test ROMs that check bit 6 and bit 0's effect on the window's "scanline counter"?

@allkern
Copy link
Member Author

allkern commented Apr 26, 2021

You mean bit 5? Matt's dmg-acid2 tests this behavior here however he doesn't really go into detail on why there should be an internal window line counter, that's why I thought this should be documented here.
And I'm not sure about bit 0 stopping the counter, I'll ask him right now

@allkern
Copy link
Member Author

allkern commented Apr 26, 2021

Fixed

@allkern
Copy link
Member Author

allkern commented Apr 26, 2021

Matt confirmed to me that the window is still activated when LCDC.0 is reset, bit 5 is the one to care about. Got rid of that bit 0 info

@ISSOtm
Copy link
Member

ISSOtm commented Apr 26, 2021

Do you have a source for that? I mean something that would be quoted/linked to within the docs, as per #66.

@mattcurrie
Copy link
Member

Do you have a source for that? I mean something that would be quoted/linked to within the docs, as per #66.

You may be familiar with this test, which checks the duration of mode 3 with LCDC.5 set and LCDC.0 not set 😉

https://github.com/mattcurrie/mealybug-tearoom-tests/blob/master/src/ppu/win_without_bg.asm

@mattcurrie
Copy link
Member

But yes, a specific test for whether the window's internal line counter is actually incremented when it is activated with LCDC.0 not set would be good too.

@ISSOtm
Copy link
Member

ISSOtm commented Apr 26, 2021

This would be good enough for the time being, imo.

@avivace avivace self-requested a review April 27, 2021 08:53
Copy link
Member

@avivace avivace left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me! Great use of the tip box

@avivace avivace merged commit 7473e2c into gbdev:develop Apr 27, 2021
@allkern allkern deleted the patch-1 branch April 28, 2021 02:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants