Duncan Webb wrote:
> A Mennucc wrote:
>
>> hi, I checked thru the code, and saw that 'ENTER' is actually used in
>> few points around; so yesterday I prepared this patch (that is only a
>> first draft) against SVN. (This patch does not apply to 1.8.3 in one
>> easily fixable point).
>>
>> Here i
A Mennucc wrote:
> hi, I checked thru the code, and saw that 'ENTER' is actually used in
> few points around; so yesterday I prepared this patch (that is only a
> first draft) against SVN. (This patch does not apply to 1.8.3 in one
> easily fixable point).
>
> Here is the rationale. I have 4 remot
On Mon, 5 Jan 2009, A Mennucc wrote:
> I wrote the patch before reading your answers, please comment on it,
> at the same time I will try to change it to reflect any ideas of you.
>
> a.
the logic appeals to me
I have got used to using E for menu on my 104 key remote but could use other
keys like
On Mon, Jan 5, 2009 at 4:49 AM, A Mennucc wrote:
> hi, I checked thru the code, and saw that 'ENTER' is actually used in
> few points around; so yesterday I prepared this patch (that is only a
> first draft) against SVN. (This patch does not apply to 1.8.3 in one
> easily fixable point).
>
> Here
hi, I checked thru the code, and saw that 'ENTER' is actually used in
few points around; so yesterday I prepared this patch (that is only a
first draft) against SVN. (This patch does not apply to 1.8.3 in one
easily fixable point).
Here is the rationale. I have 4 remotes for modern player devices;
On Sun, 2009-01-04 at 16:27 +, John Molohan wrote:
> I think some of the confusion here might be on the word chosen for 'e' -
> ENTER, I think it could be replaced by a function called INFO. 'e'
Agreed. This was a source of confusion for me since my first day of
using Freevo.
---
Duncan Webb wrote:
> John Molohan wrote:
>
>> A Mennucc wrote:
>>
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> A Mennucc ha scritto:
>>>
>>>
Moreover the way these two events are mapped to my remote and to the
keyboard is a bit messy IMHO.
John Molohan wrote:
> A Mennucc wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> A Mennucc ha scritto:
>>
>>> Moreover the way these two events are mapped to my remote and to the
>>> keyboard is a bit messy IMHO.
>>>
>> let me be more explicit...
>> the confusion (for me) ar
A Mennucc wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> A Mennucc ha scritto:
>
>> Moreover the way these two events are mapped to my remote and to the
>> keyboard is a bit messy IMHO.
>>
>
> let me be more explicit...
> the confusion (for me) arises from the fact that
> the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
A Mennucc ha scritto:
> Moreover the way these two events are mapped to my remote and to the
> keyboard is a bit messy IMHO.
let me be more explicit...
the confusion (for me) arises from the fact that
the key 'enter' is mapped to the event SELECT
the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hi,
hi, I have always wondered, what is the rationale of the 'ENTER' and
'SELECT' events?
When I configured my remote, some years ago, I was confused by having
those two different events.
Today I was reading thru event.py, and I again fail to prope
11 matches
Mail list logo
