Curve editor bugs / nusenses

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Access the CURVES menu 
2. Press [MENU] on any curve to enter edit node
3. Press [DOWN] to move to the first field

Bug 1: Note that pressing [LEFT] or [RIGHT] works fine on the field itself, but 
also moves the curve point selector on the graph around the place, as if we 
were in the "EDIT-> mode.

Bug 2: Whilst NOT in the graphics 'EDIT->' mode, the [UP] and [DOWN] keys are 
supposed to move up and down the fields, while [LEFT] and [RIGHT] decrease and 
increase the field values. However, since we seem to get put into a half 
'EDIT->' mode after clicking [LEFT] or [RIGHT] the first time, we then get 
stuck in edit mode for the field as if we were accessing the point on the 
graph, which then means we have to press [EXIT] before we can move to another 
field.

In summary then, the 'EDIT->' graphical point-selection mode is being entered 
when it should not be. This seems to happen when the first change of value is 
made in any field.

What is the expected output? What do you see instead?

Please use labels and text to provide additional information.

Original issue reported on code.google.com by gru...@gmail.com on 16 Oct 2011 at 8:06

[GoogleCodeExporter]

Please ignore the strike-trough on the Bug 1 and Bug 2, above. 

Google code apparently considers Bug 1 as a synonym for Issue 1. I meant only, 
'Bug One' and 'Bug Two', with no intended reference to Issue 1 or Issue 1.

Original comment by gru...@gmail.com on 16 Oct 2011 at 8:08

[GoogleCodeExporter]

Fixed in r1177, coincidentally after bsongis found the same bug, but with 
different symptoms.

Original comment by gru...@gmail.com on 17 Oct 2011 at 4:49

• Changed state: Verified
• Added labels: Milestone-frsky-October2011StableReleaseTargete
• Removed labels: Milestone-frsky

[GoogleCodeExporter]

Original comment by gru...@gmail.com on 17 Oct 2011 at 4:51

• Added labels: Milestone-frsky
• Removed labels: Milestone-frsky-October2011StableReleaseTargete