Opened 3 years ago

Closed 3 years ago

#11651 closed defect (fixed)

XO-1.75 keyboard test exit marker misplaced when run from menu

Reported by: Quozl Owned by: Quozl
Priority: normal Milestone: 1.75-firmware
Component: ofw - open firmware Version: Development build as of this date
Keywords: Cc:
Blocked By: Blocking:
Deployments affected: Action Needed: no action
Verified: no

Description

The exit marker for the escape key is correctly placed when using test /keyboard, but appears over the fn key when using menu.

Change History (4)

comment:1 Changed 3 years ago by Quozl

  • Action Needed changed from diagnose to add to release

The exit marker is placed using "0 d# 13 at-xy" in draw-keyboard. The test is defined as a graphics mode test, and this type of test does not reset the scroll region of the display. Changing it back to a text mode test fixes this, in svn 2877.

comment:2 Changed 3 years ago by martin.langhoff

James -- is this in an rpm already that I can add to an OS build? If so, mark it "add to build".

If it's in a commit that needs to go into an OFW release, please use a different action ("package" is probably the most appropriate).

The scope/perspective for the "action" field is is the overall OS release -- that's how we treat it within this project...

thanks!

comment:3 Changed 3 years ago by Quozl

  • Cc wmb@… added

no, for the 1.75-firmware milestone, and other -firmware milestones, i have been using add-to-release and other next action values in their literal sense, relating only to openfirmware. the ticket will close on a release of openfirmware, unless testing of the fix was warranted.

if the bug reporter or triage had placed this ticket in the 11.3.1 milestone, then i would expect to have this ticket in package state.

if you would like the ticket fixed in 11.3.1, then please say so.

comment:4 Changed 3 years ago by Quozl

  • Action Needed changed from add to release to no action
  • Cc wmb@… removed
  • Resolution set to fixed
  • Status changed from new to closed

Is in Q4D05.

Note: See TracTickets for help on using tickets.