Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make Logitech Keyboard compatible with display nodes other than head-node (42-a) #381

Open
Jbuhgit opened this issue May 30, 2018 · 2 comments

Comments

@Jbuhgit
Copy link

Jbuhgit commented May 30, 2018

Overview:
The Logitech keyboard that is currently being tested on ISO version 2.11.0-rc15. The keyboard is functional however the cursor that appears when using the Touchpad on the keyboard, only allows the cursor to exist on 42-a nodes (tested @ ephq) .

Requirements:
List of requirements that need to be satisfied that are needed to consider this feature implemented.

  • Cursor should be able to move from L1 / R1 to other displays setup on other display nodes (42-b)
  • Cursor is able to navigate across all 7 screens.
  • Cursor does not get stuck on 3 center screens.

Testing scenario

  • Using touchpad on Logitech keyboard , test whether the cursor is able to move across all screens on LG.
@Jbuhgit Jbuhgit closed this as completed Nov 8, 2018
@Jbuhgit Jbuhgit reopened this Jun 26, 2019
@jandro-air
Copy link
Contributor

Looks like this continues to be an issue. Following case:

User attempts to use Logitech keyboard to access a webpage on the outer 4 screens of an LGX (42-b). They cannot, because the cursor has been limited to the center three screens (42-a). The cursor stops at the borders of the R1 and L1.

We have verified that systems that experience this are using the correct ros nodes. It would be good to see if we can prevent this from happening at all to provide a more seamless experience.

@jandro-air
Copy link
Contributor

allegedly resolved by @FuriousJulius and @mvollrath on bionic iso

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants