On Sun, 11 Sep 2011 04:25:57 -0400 Youness Alaoui
said:
strings are easier to maintain (no header-from-hell to maintain with every
possible key on every possible system defined as a number). and reality is you
never know the #defined keysym until you press the key on the kbd and find out
the even
bject: Re: [E-devel] ecore/evas key events
Bump?
Is there no one who knows why this was designed this way ? David and I both
seem to agree that this isn't the right way to go.
On Sun, Sep 11, 2011 at 7:46 AM, David Seikel wrote:
> On Sun, 11 Sep 2011 04:25:57 -0400 Youness Al
Bump?
Is there no one who knows why this was designed this way ? David and I both
seem to agree that this isn't the right way to go.
On Sun, Sep 11, 2011 at 7:46 AM, David Seikel wrote:
> On Sun, 11 Sep 2011 04:25:57 -0400 Youness Alaoui
> wrote:
>
> > While I'm working on adding keyboard suppo
On Sun, 11 Sep 2011 04:25:57 -0400 Youness Alaoui
wrote:
> While I'm working on adding keyboard support to ecore/ecore-evas for
> the ps3 engine, I noticed that there is no enum for the various keys,
> they are strings instead. I do not understand *why* this is done this
> way... first of all, do
