69
edits
Difference between revisions of "User:Seldon/GSoC2007-ProjectDiary"
User:Seldon/GSoC2007-ProjectDiary (view source)
Revision as of 08:59, 3 August 2007
, 08:59, 3 August 2007discussion with SEV on points no. 4 and 6 from the key mapper features list, reinstalling the software
(working on key mapper features list) |
(discussion with SEV on points no. 4 and 6 from the key mapper features list, reinstalling the software) |
||
| Line 130: | Line 130: | ||
2) possibility to completely unassign key from some particular action; | 2) possibility to completely unassign key from some particular action; | ||
3) checks for the same key being assigned to different actions; | 3) checks for the same key being assigned to different actions; | ||
4) there should be a way to define the engine and game actions (like game data files, etc.); | 4) there should be a way to define the engine and game actions (like in game data files, etc.); | ||
5) action mapping priorities (if there is no mapping for these actions the game won't start or smth like this. The situation when actions with lower priority have mappings while the actions with higher priority don't won't be allowed.) | 5) action mapping priorities (if there is no mapping for these actions the game won't start or smth like this. The situation when actions with lower priority have mappings while the actions with higher priority don't won't be allowed.) | ||
6) more then one keymap (as for Indy games); | 6) more then one keymap (as for Indy games); | ||
| Line 137: | Line 137: | ||
Today I have implemented the saving and loading of action mappings to and from the scummvm config file. I have also added the new key mapper tab to the edit game dialog with the buttons and action list. I have also thought over most of the implementation details for the above mentioned features. | Today I have implemented the saving and loading of action mappings to and from the scummvm config file. I have also added the new key mapper tab to the edit game dialog with the buttons and action list. I have also thought over most of the implementation details for the above mentioned features. | ||
== 2007- | == 2007-08-01 (Wednesday) - working on key mapper features listed above == | ||
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-2 (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: | |||
* in order to save a mapping we need to store a key and an action; | |||
* to store a key it's enough to store its keycode and the flags; | |||
* so it's a 6 digit hexadecimal number; | |||
* an action could also be identified by it's default key; | |||
* so it's another 6 digit hexadecimal number; | |||
* this approach is compact and we can save all mapping in one string, and then easily parse it, since we have the fixed length for all elements (I got the idea for it from gui/Action.h save/loadMapping functions); | |||
* this string is then saved under [scummvm] for global mappings; | |||
* and under say [sky] for game mappings; | |||
* actions with identical default keys are dissalowed within single game. | |||
Here are the SEV's comments regarding the key map sets (for Indiana Jones fighting, i.e.): | |||
<_sev> I recommend to show those sets on tabs in keymapper dialog | |||
<_sev> it's simple to implement and will not clobber your output | |||
<_sev> in 90% of cases there will be a single set | |||
<_sev> but rest 10% belong to quite important set of games: | |||
<_sev> indiana jones -> fighting | |||
<_sev> gobliiins -> password entry | |||
<_sev> there also should be way to disable all mappings temporarily | |||
<_sev> say, when user uses predictive dialog | |||