Hi All,

One thing I have noticed is when two monitors of differing resolutions are enabled, in my case the DSI and HDMI 0, an external mouse works fine on both screens in a typical "extended desktop" mode but the touch pad does not follow this mapping.? Although the DSI screen is working fine, what appears to be happening is the touchpad is mapped to control both monitors and not just the DSI display.? This appears to create a mapping error between the touchpad and the resolution of the DSI screen.? When the mouse pointer is moved by the external mouse and it transitions between monitors, it follows/translates the change in position without display errors.? By contrast, if you use the touchpad to move the pointer similarly, when you touch the screen, the pointer jumps to a position on the screen away from your intended touch. It appears that when two monitors are active, the touchpad follows the area combination of the two monitors and not just the DSI driven display.? That means the touchpad pointer does not align with the various functions and thus is unusable.

?I hope I made sense in describing the behavior.? Does anyone know of a way to correct this mapping issue or limit the touchpad mouse function to just the DSI display?

Thanks, Scott??

Hey ecc,

That was the solution!? It was pretty simple: tell the OS to only use the touchpad mouse on the DSI screen and every thing lines up.

In my case the terminal command is: xinput map-to-output "raspberry-ts" "DSI-1".? I'm pretty sure that once I restart the RPI that setting will be lost but this makes the touchpad useable in multiple monitor configurations.? I'll have to see how to make it part of the boot sequence.

Thanks for the help, Scott

Hey Ashhar (or anyone else),

I am uncertain where it would be best to add this mouse mapping to the RPI/sBitx boot sequence.? Can you make a recommendation?

Thanks, Scott

Hi Jerry,

I'll have to find the appropriate files and add the command.? I'm really kind of green when it comes to Linux.? It sort of "feels" like DOS but different.? I never had the need to really learn it but now I need to learn a bit more.? Ol' dogs and tricks, right?

Thanks, Scott

.profile and .bashrc? are where you'd put commands that you want to run upon >>user login<<.??

xinput is an executable file (program) that modifies the established X windowing environment.

rather than wait until after the X environment is set up (for all users), then modifying it via xinput (just for the user pi), you could simply specify the desired configuration in the X windowing initialization process.? (these rules are usually stored in the /usr/share/X11/xorg.conf.d/ directory).

On 8/23/22 19:12, JerryP wrote:

The files, .profile and .bashrc,? are "hidden" files because they are preceded?by a '.' and usually won't be displayed in a terminal unless you use the command "ls -la". A gui file manager don't show them either unless you turn on view hidden files. You can edit the files from a terminal command prompt using "nano .bashrc". Use ctrl-x to exit after your edits to save and exit nano. I don't remember if the file manager in PI-OS shows hidden files.

On Tue, Aug 23, 2022 at 5:45 PM Scott KE8KYP <scott_massey@...> wrote:

Hi Jerry,

I'll have to find the appropriate files and add the command.? I'm really kind of green when it comes to Linux.? It sort of "feels" like DOS but different.? I never had the need to really learn it but now I need to learn a bit more.? Ol' dogs and tricks, right?

Thanks, Scott

--

Jerry, AC9NM

手中的鸟在灌木丛中值两个