Explorer
11 May 2010, 13:21
I personally think this is a bug rather than a feature request.
The ".WAgame" file extension is (re-)associated each time I start WA. However, this should be done during installation and not during run-time. What I mean is that the "update installer" should create the file association when updating WA, and the WA.exe should stop doing so when running. This will allow users to tweak the registry for their needs. (associating with WormKit, applying the Thumbnail Extension, etc.)
Also, an "open" shell command should be present for most file extensions. Some programs will only recognize the "open" command when opening files. Why I say this is that Safari, the browser I'm using, will fail (and eventually crash) when it tries to open the ".WAgame" file I just downloaded. Therefore, I suggest that the registry key [HKCR\Team17.WAgame\shell\a.play] should be renamed to [HKCR\Team17.WAgame\shell\open] to solve the problem.
That's the two issues I've seen. Sorry for bad English.
The ".WAgame" file extension is (re-)associated each time I start WA. However, this should be done during installation and not during run-time. What I mean is that the "update installer" should create the file association when updating WA, and the WA.exe should stop doing so when running. This will allow users to tweak the registry for their needs. (associating with WormKit, applying the Thumbnail Extension, etc.)
Also, an "open" shell command should be present for most file extensions. Some programs will only recognize the "open" command when opening files. Why I say this is that Safari, the browser I'm using, will fail (and eventually crash) when it tries to open the ".WAgame" file I just downloaded. Therefore, I suggest that the registry key [HKCR\Team17.WAgame\shell\a.play] should be renamed to [HKCR\Team17.WAgame\shell\open] to solve the problem.
That's the two issues I've seen. Sorry for bad English.