[v1.60] File Associations, valid.ext, and the Power User
Posted: Mon May 10, 2021 3:04 pm
So, to get straight to the point… does the latest Windows release build of Snes9x – v1.60 (Apr 25, 2019), as of this post – still make itself the default program for several arbitrary file types upon running? If so… why?
It's really frustrating to think that such a glaring oversight which turned so many people away would remain largely ignored by the devs. I mean, really. When the best solution is to edit your registry and modify the "valid.ext" file that the emulator generates only after being run, that speaks volumes about what how the staff looks at its patrons. Yes, you may not see it as "a big problem" because, honestly, only "power users" like me and those who've complained would find it frustrating to deal with… but that doesn't mean it's okay for your emulator to just sink its claws into, like, twenty-or-thirty different filetypes which may or may not be directly related to Super NES/Famicom and Broadcast Satellaview emulation.
So… yeah. Does the latest version still do that? 'cause if it does, I'd like to suggest adding a "valid.ext" in future release ZIPs and maybe make a note of what it is and does in the readme. Ya know… since it's not already mentioned. Like… anywhere.
~ J
It's really frustrating to think that such a glaring oversight which turned so many people away would remain largely ignored by the devs. I mean, really. When the best solution is to edit your registry and modify the "valid.ext" file that the emulator generates only after being run, that speaks volumes about what how the staff looks at its patrons. Yes, you may not see it as "a big problem" because, honestly, only "power users" like me and those who've complained would find it frustrating to deal with… but that doesn't mean it's okay for your emulator to just sink its claws into, like, twenty-or-thirty different filetypes which may or may not be directly related to Super NES/Famicom and Broadcast Satellaview emulation.
So… yeah. Does the latest version still do that? 'cause if it does, I'd like to suggest adding a "valid.ext" in future release ZIPs and maybe make a note of what it is and does in the readme. Ya know… since it's not already mentioned. Like… anywhere.
~ J