1,079
edits
Difference between revisions of "Talk:Keymapping Improvements"
no edit summary
m |
|||
| Line 9: | Line 9: | ||
* Maybe there should be a way for the backend to report what buttons (if any) it binds to the actions so that the help screens can contain accurate information? (After all, the help screens are generated by the engine, not the backend.) | * Maybe there should be a way for the backend to report what buttons (if any) it binds to the actions so that the help screens can contain accurate information? (After all, the help screens are generated by the engine, not the backend.) | ||
--[[User:Marcus|Marcus]] 17:28, 1 July 2007 (CEST) | --[[User:Marcus|Marcus]] 17:28, 1 July 2007 (CEST) | ||
Hi Marcus, to reply to your above remarks: | |||
* Fully agreed. The updated plan (see also my email on scummvm-devel) includes a 'priority' field in the list of actions. Alternatively, we could just "sort" that list by priority. But I prefer the priority field (nothing stops us from doing both, anyway, it's a simple as coding a 'sort' for the list -- I guess I am lossing myself in technical details here ;-) | |||
* Gradual conversion scheme: Aye, that is indeed a problem. But the update plan suggest that the backend just generates key events anyway, instead of introducing a new event type, so I ''think'' that problem is dealt with. Please correct me if I am wrong. | |||
* A popup menu with unmapped actions sounds like a sweet plan. It could also use the priority for sorting. | |||
* The "help dialog" AFAIK only exists in the SCUMM engine, and isn't so great. I think it would be "better" to leave such a thing to the backend (but of course the code for that dialog could be shared). Or just display the generic "key remapping" dialog which I suggested in my last email to scummvm-devel. | |||
--[[User:Fingolfin|Fingolfin]] 17:45, 1 July 2007 (CEST) | |||