9front - general discussion about 9front
 help / color / mirror / Atom feed
From: qwx <qwx@sciops.net>
To: 9front@9front.org
Subject: Re: [9front] proposal: move common code from md, nes, snes, gb, gba, c64 to a libemu
Date: Fri, 11 May 2018 13:08:32 +0200	[thread overview]
Message-ID: <DC285D14F22CBA1FAF703EDCE06940A4@wopr.sciops.net> (raw)
In-Reply-To: alpine.LNX.2.00.1805111137160.15422@phi

> > - (?) added toggling fullspeed emulation when audio is enabled
> by dropping samples?
> 
> i don't like that this is enabled with space.
> i would prefer some more remote key, like `.
> 
> personally i think this is a misfeature. in other emulators i always find 
> myself using it too much.

I agree, ` is better.  I'd like to keep this just because it lets me
blaze through some extremely annoying unskippable sequences in many
games (for convenience rather than a hack).  Final verdict?


> > - (?) dynamic rescaling from x1 to x16 for larger screens;
> >  removed -2, -3
> i think i've stated before i don't like this very much.
> but i'll accept it begrudgingly, i think :).

Thank you :)


> > - emalloc, as often reproduced in the emulators;
> >  might be better off in libc or nowhere
> moving emalloc to libc has been discussed many times and vetoed every
> time.
> not sure what you mean by 'nowhere'.

I recall the debates;  I just wasn't sure if it was worth placing in the
library anyway, or to just leave it in the emulators that need it.  I'm
leaning towards just removing it from libemu, it's a bit extraneous.


> > - the signed typedefs might be better placed in /$objtype/include/u.h
> yes i would like that.
> we've postponed doing this too many times already.

So, can we?  I don't remember why it was never done.  What objections
were there?


> > - clumsy; input bit vectors are semi-arbitrary and adaptation in some
> >  emulators is fairly bad; worse examples: snes and md
> > - regkeyfn is not very useful as is
> i would like this to be fixed.
> why not just register all keys?
> something like
>  	regkey("left", Kleft, 1);
> to register it as bit 1 in the input bitvector.

True, this makes more sense.  I'll do it.


> > - can we merge 2600 even if it's buggy?
> yes.

I will then do it after all is said and done for libemu.


Thanks!

qwx


             reply	other threads:[~2018-05-11 11:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-11 11:08 qwx [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-05-13  5:04 qwx
2018-05-12 19:49 qwx
2018-05-12 18:19 cinap_lenrek
2018-05-12 18:00 cinap_lenrek
2018-05-11 20:18 qwx
2018-05-11  7:39 qwx
2018-05-11  9:57 ` [9front] " Julius Schmidt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DC285D14F22CBA1FAF703EDCE06940A4@wopr.sciops.net \
    --to=qwx@sciops.net \
    --cc=9front@9front.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).