69
edits
Difference between revisions of "User:Seldon/GSoC2007-ProjectDiary"
User:Seldon/GSoC2007-ProjectDiary (view source)
Revision as of 09:04, 3 August 2007
, 09:04, 3 August 2007→2007-08-02 (Thursday) - discussion with SEV on points no. 4 and 6 from the key mapper features list, reinstalling the software
(discussion with SEV on points no. 4 and 6 from the key mapper features list, reinstalling the software) |
|||
| (One intermediate revision by the same user not shown) | |||
| Line 140: | Line 140: | ||
Today I have cleared the 2nd and 3rd point from the requirements list, in course of that work no. 7 was also partially cleared. I have been actively working on No. 1 today. Item 5 is not big and will be implemented in the course of work on no. 1. With regards to no. 4, I have fixed key mappings save/load functionality to save the mappings under the specific game domains. | Today I have cleared the 2nd and 3rd point from the requirements list, in course of that work no. 7 was also partially cleared. I have been actively working on No. 1 today. Item 5 is not big and will be implemented in the course of work on no. 1. With regards to no. 4, I have fixed key mappings save/load functionality to save the mappings under the specific game domains. | ||
== 2007-08- | == 2007-08-02 (Thursday) - discussion with SEV on points no. 4 and 6 from the key mapper features list, reinstalling the software == | ||
Today I have talked to SEV about the place where to define the engine and game actions. They will be defined in the game data files and retrieved using common/advancedDetector.cpp static void updateGameDescriptor(). The key maps storing algorithm is as follows: | Today I have talked to SEV about the place where to define the engine and game actions. They will be defined in the game data files and retrieved using common/advancedDetector.cpp static void updateGameDescriptor(). The key maps storing algorithm is as follows: | ||
* in order to save a mapping we need to store a key and an action; | * in order to save a mapping we need to store a key and an action; | ||
| Line 153: | Line 153: | ||
Here are the SEV's comments regarding the key map sets (for Indiana Jones fighting, i.e.): | Here are the SEV's comments regarding the key map sets (for Indiana Jones fighting, i.e.): | ||
I recommend to show those sets on tabs in keymapper dialog: it's simple to implement and will not clobber your output. In 90% of cases there will be a single set but rest 10% belong to quite important set of games: | |||
* indiana jones -> fighting | |||
* gobliiins -> password entry | |||
There also should be way to disable all mappings temporarily, say, when user uses predictive dialog. | |||