suddenly (actually, it’s been a while since i’ve made c64 disk images so i can’t say how suddenly) when i compile an ‘aastory’ into a c64 disk image, this happens:
> >MBCZ
that is, everything works perfectly until i hit the SPACE bar and instead of a space i get that “>MBCZ”.
i don’t think this is a VICE/emulation problem as hitting space-bar outside of the interpreter works normally.
i’ve gone back and tried this with several dialog games, compiling them to aastory and making C64 images, but get the same result, always with the same > MBCZ instead of a space.
i’m using the prebuilt macos aambundle from the “public” dialog repository.
What happens if you use the old aambundle from Linus’s site? All the keyboard-matrix reading happens in scankeyboard in c64_frontend.s, and that’s not something I’ve touched since the community fork.
Yeah, you’ll need a file from an earlier Å-machine. There’s one in /examples in the Å-machine distribution. That also comes with a disk image produced with an earlier aambundle.
I haven’t been able to reproduce this though. Any files I run through current aambundle work properly in VICE.
it doesn’t do it using the SDL2 version, only the GTK3 version. i don’t know the different underpinnings of the two versions but, yes, it does seem to be a VICE problem, specifically, a macos GTK3 version.