Develop

Ticket #485 (closed defect: fixed)

Opened 3 years ago

Last modified 2 years ago

APP keys don't work for mode=infobox

Reported by: Ingenieur Owned by: max
Priority: normal Milestone: XCSoar 6.0.x
Component: Configuration Version: 6.0a
Keywords: Input Event, Infobox Cc:

Description

Trying to modify a customized MyConfig?.xci i found the following problem:

putting the following on the top of the config file does not work:

mode=infobox
type=key
data=APP1
event=StatusMessage APP1 in infobox

The APP key is not recognized, not matter if it is APP1, APP2,...
I would like to use this to toggle through the infobox groups.
If i replace APP with LEFT, RIGHT, UP, DOWN it works fine.

Attachments

TestCfg2.xci (2.2 KB) - added by Ingenieur 3 years ago.
My XCI file, as it produces the problem

Change History

comment:1 Changed 3 years ago by Ingenieur

  • Priority changed from highest to normal

comment:2 Changed 3 years ago by max

  • Owner set to max
  • Status changed from new to assigned

Fixed in a00b310ae6056edfd8d0ef4f83f77e2f9664b19c

comment:3 Changed 3 years ago by max

  • Status changed from assigned to closed
  • Resolution set to fixed

comment:4 Changed 3 years ago by Ingenieur

  • Status changed from closed to reopened
  • Resolution fixed deleted

In WM6.0-a5 i still have problem to use the APP* keys in combination with Infoboxes on my PDA. The following code in an *.xci works fine:

mode=infobox
type=key
data=RIGHT
event=ChangeInfoBoxType next

mode=infobox
type=key
data=LEFT
event=ChangeInfoBoxType previous

Whereas the following code does not work:

mode=infobox
type=key
data=APP2
event=ChangeInfoBoxType next

mode=infobox
type=key
data=APP3
event=ChangeInfoBoxType previous

I attach my xci file as a reference. All other configuration in this file works fine.

Changed 3 years ago by Ingenieur

My XCI file, as it produces the problem

comment:5 Changed 2 years ago by Turbo

  • Status changed from reopened to assigned

comment:6 Changed 2 years ago by max

  • Status changed from assigned to closed
  • Resolution set to fixed

Another attempt, please reopen if it still fails for you.

Fixed in c546a4ab197d1be1583ae5acd048c0863e1c6ef1

Note: See TracTickets for help on using tickets.