Ticket #10534 (new defect)

Opened 3 years ago

Last modified 3 years ago

F5/F6 key mappings should not apply to XO-1.5

Reported by: martin.langhoff Owned by: erikos
Priority: normal Milestone: 11.3.0
Component: sugar Version: not specified
Keywords: Cc: pgf
Action Needed: never set Verified: no
Deployments affected: Blocked By:
Blocking:

Description

In 10.1.2 we added keyboard mappings that should only apply to XO-1.5HS keyboards.

These are

  • F5 maps to the 'search' key (right now calls the journal)
  • F6 maps to the 'frame' key

These mappings are showing up on a conventional XO-1.5 , and get in the way of potential usage of F5 to F8.

Change History

  Changed 3 years ago by mikus

These mappings ... get in the way of potential usage of F5 to F8.

True -- but *are* there application (e.g., Activity) uses of F5 to F8 ?

For three years now I've been setting Sugar key mappings in the F5 to F8 range for Frame and for Journal, because I use external USB keyboards with my XOs which do not otherwise have function-keys for these functions. In all this time I have NOT encountered any applications (run under the Sugar window manager) which have been impacted by those function-keys being diverted.

[If I remember correctly, there *have* been applications impacted by F9 to F12 having being diverted to Sugar's brigtness-level control and volume-level control.]

follow-up: ↓ 4   Changed 3 years ago by Quozl

You will need to deal with upstream here, since Sugar Labs adopted the change in master just prior to 0.90, see 66855e4. Other users of Sugar will have benefited from the change. See also the 0.90 New Keybindings section of the release notes. Horse has bolted and you're swimming against the rip.

in reply to: ↑ 3   Changed 3 years ago by pgf

Replying to Quozl:

Horse has bolted and you're swimming against the rip.

i'm trying to figure out what component i should assign for "atrociously mixed metaphor"... points for good visuals, though.

follow-up: ↓ 6   Changed 3 years ago by erikos

Not nice, but I think dealing with this can wait.

in reply to: ↑ 5   Changed 3 years ago by erikos

Replying to erikos:

Not nice, but I think dealing with this can wait.

(this is about getting a fix in for 10.1.3)

Note: See TracTickets for help on using tickets.