| [gluon] FW: Input Actions for Gluon Input GCI Task |
[ Thread Index |
Date Index
| More lists.tuxfamily.org/gluon Archives
]
- To: <gluon@xxxxxxxxxxxxxxxxxxx>
- Subject: [gluon] FW: Input Actions for Gluon Input GCI Task
- From: "Tony Young" <rofflwaffls@xxxxxxxxx>
- Date: Wed, 1 Dec 2010 13:49:46 +1300
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:from:to:references :in-reply-to:subject:date:message-id:mime-version:content-type :content-transfer-encoding:x-mailer:content-language:thread-index; bh=hrANaLh78hOpBP8zG2ymCIN4eDUyR1F/eUs3VzEvxSk=; b=hU1DZ8AVo3kfVhXHyahvTNH8gOcUDCw+OjF/01mXFemYtZWNzm25T8LjcHBVAdysOd 2lqpYC/bGvAxRehaCL5zLc6P4LxcstFErGKGW+OAkSHmQggHEfjxUESBQvxd97SIatM2 HQfDp8vE6c7qrrKY7BG7ILHBh4dmZdwhbWWGc=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=from:to:references:in-reply-to:subject:date:message-id:mime-version :content-type:content-transfer-encoding:x-mailer:content-language :thread-index; b=N5NXwzH+DaaQiMbW61NSS7akSPlcn79NVG/niJb6f7WMv8OhJMWiSa5nm5Gn0epa2a w72SWmEpG+G7+pIk9T3uv/qcWEZfeFGsxfYUVOu7D8FkvAtwuLwxQzWmNw2J6txQETXu 0cxQwI+fjBj9c88lXWp1edOVcwf3JEuHzcbFA=
- Thread-index: AQJW5B2TtYVcBUKGBcb49YK4EIkV45J0Glgg
Whoops, forgot to subscribe before sending this.
> -----Original Message-----
> From: Tony Young [mailto:rofflwaffls@xxxxxxxxx]
> Sent: Wednesday, 1 December 2010 1:44 p.m.
> To: 'Arjen Hiemstra'
> Cc: 'gluon@xxxxxxxxxxxxxxxxxxx'
> Subject: Input Actions for Gluon Input GCI Task
>
> Hi there,
>
> I would just like to ask a few questions regarding the Google Code-In
task:
> http://www.google-
> melange.com/gci/task/show/google/gci2010/kde/t129021691853
>
> From the conversations I've had with leinir and djszapi in #gluon, I've
> come up with http://pastebin.com/b8Z6FiF6
>
> There are no GluonInput-specific implementations in the code and it's very
> generic. It uses Qt signals for notifying anything interested in input
> actions and, by overriding checkActionState of InputAction, one can
> determine if their action has triggered or not, and which state it's in
> (Up or Down) by calling update on the InputAction every frame (simplified
> by using InputActionManager).
>
> An action can be created by subclassing InputAction and overriding the
> pure virtual method checkActionState which returns either None, Up or Down
> depending on the action's state.
>
> What I'm not sure about is whether or not if I actually need to implement
> any interface to GluonInput. I've been told that I don't need to, and an
> abstract implementation of actions is fine, but since this is your task
> I'd like to just check with you.
>
> Waiting for your reply,
> Tony
---
+----------------------------------------------+
Gluon is a high-level game development library for the KDE desktop enviornment.
http://gluon.tuxfamily.org/
http://gitorious.org/gluon