Re: Retroarch is now accessible
Please read:
Okay, a few things about posting issues on Github. I'm not pointing fingers, I just want to get this straightened before this becomes the norm. @barryRo, please correct me if I get anything wrong.
First: When you make an issue, please detail as much as you can. If possible, paste a log or attach it, or put it in a gist a link to it. When you detail the problem, list your Windows version, do "winver" in the Run dialog to get this information. Detail your computer hardware, Retroarch version (or nightly file name or date and time of download). List the Rom and core you were using when the problem occurred.
Second, do *not* demand anything from the Retroarch developers. Asking is great, but these people do this as a hobby, and even if you pay them for this, you should not demand that a problem be fixed right now. Be kind to these people, I beg all of you. They work very hard, not only to develop accessibility features for us, but to test them, and ask us any questions they may need to make things great for us.
And, always remember that accessibility isn't the only thing they do. They're always adding new cores, fixing old ones, updating cores, adding visual shaders, cleaning up their code, and then blogging and making videos about these improvements. Well, I mean, I wrote and did the video for the accessibility one, but yeah. These people are passionate about what they do, and we should not make them cynical about us by posting as if we were their boss. Hint, we're not. We're gamers just like them, and we should work together for the accessibility of retro video games. I mean, who doesn't wish that they could play Final Fantasy 7?
-- Audiogames-reflector mailing list Audiogames-reflector@sabahattin-gucukoglu.com https://sabahattin-gucukoglu.com/cgi-bin/mailman/listinfo/audiogames-reflector
