|Re: [hatari-devel] New SYNC release - new comment on emulation :)|
[ Thread Index |
| More lists.tuxfamily.org/hatari-devel Archives
- To: hatari-devel@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [hatari-devel] New SYNC release - new comment on emulation :)
- From: Troed Sångberg <troed@xxxxxxxxxxx>
- Date: Sun, 16 Aug 2020 12:52:13 +0000
- Authentication-results: mail-40131.protonmail.ch; dkim=none
* No borders (many demos, some games and utilities might require this to be on)
* Atari SC1224 and SM124 border size
* Maximum size borders (extreme demos and for developers)
Something like that? And maybe an indication to show when an "event" happens outside of currently displayed borders. For that purpose we can ignore simple border color shifts and only care about graphics when in the "no border" case.
Sent from ProtonMail Mobile
On Sun, Aug 16, 2020 at 14:43, Thomas Huth <th.huth@xxxxxxxxx
Am Sun, 16 Aug 2020 13:59:01 +0200
schrieb Nicolas Pomarède <npomarede@xxxxxxxxxxxx>:
> Le 16/08/2020 à 11:15, Thomas Huth a écrit :
> >> As pointed in the other part of this thread, those extra lines
> >> won't be displayed for now, because Hatari needs a more flexible
> >> way to increase window's height.
> > We already have ConfigureParams.Screen.nMaxHeight, so IIRC users can
> > already adjust the maximum height of the borders with that
> > setting... could this simply be extened to these additional lines
> > now, too?
> I think nMaxHeight is not enough, because we want to specify separate
> values for height in top order and height in bottom border. Having
> only a global height for the screen is ambiguous.
> Similarly, we need one day to have separate values for the number of
> pixels to display in left and in right border ; having only a global
> width variable is not enough and is ambiguous too (because in
> overscan mode the number of added pixels is not the same in left
> border and in right border)
Hmm, we've had this in the past already, but it has been removed in
commit 460b4572ab6b7d37c8e952b99c9916acc31c3d17 ... IIRC we considered
that this was too complicated for most users, so we switched to
something more userfriendly instead. Not sure whether it's such a good
idea to re-introduce these settings...?