| 2013-06-06 14:20:52 |
Dean Lillie |
bug |
|
|
added bug |
| 2013-06-06 14:22:21 |
Dean Lillie |
description |
I have two monitors on a PC running Windows 7 x64. I have two monitors, my primary on the right, secondary to the left of it. and I set my driver to only use a single screen for input (monitor 1, 1920x1080). When using Inkscape, the input is offset, varying depending on what the resolution the secondary monitor is set to.
I actually managed to "fix" it. I opened up a memory editor, searched for the combined length of both monitors (3200 if the secondary is 1280) and changed it to 1920. After doing that, the tablet worked perfectly.
Inkscape doesn't seem to be reading screen width from the driver properly. I don't know anything about the APIs or standards involved, but if it's as simple a fix as changing a value in memory..? It's not a permanent one, the memory layout changes every time so it's inconvenient to do every time to say the least.
This happens in the nightly builds as well as the latest stable. The tablet is a Huion 580, which is basically a generic model. I'd assume the same thing happens on Monoprice tablets as well as many others since they all use interchangeable drivers. |
I have two monitors on a PC running Windows 7 x64. My primary on the right, secondary to the left of it. and I set my driver to only use a single screen for input (monitor 1, 1920x1080). When using Inkscape, the input is offset, varying depending on what the resolution the secondary monitor is set to.
I actually managed to "fix" it. I opened up a memory editor, searched for the combined length of both monitors (3200 if the secondary is 1280) and changed it to 1920. After doing that, the tablet worked perfectly.
Inkscape doesn't seem to be reading screen width from the driver properly. I don't know anything about the APIs or standards involved, but if it's as simple a fix as changing a value in memory..? It's not a permanent one, the memory layout changes every time so it's inconvenient to do every time to say the least.
This happens in the nightly builds as well as the latest stable. The tablet is a Huion 580, which is basically a generic model. I'd assume the same thing happens on Monoprice tablets as well as many others since they all use interchangeable drivers. |
|
| 2013-06-06 14:22:45 |
Dean Lillie |
summary |
tablet input inaccurate/offset when multiple monitors |
Input inaccurate/offset when using multiple monitors with some graphics tablets |
|
| 2013-06-06 14:23:08 |
Dean Lillie |
description |
I have two monitors on a PC running Windows 7 x64. My primary on the right, secondary to the left of it. and I set my driver to only use a single screen for input (monitor 1, 1920x1080). When using Inkscape, the input is offset, varying depending on what the resolution the secondary monitor is set to.
I actually managed to "fix" it. I opened up a memory editor, searched for the combined length of both monitors (3200 if the secondary is 1280) and changed it to 1920. After doing that, the tablet worked perfectly.
Inkscape doesn't seem to be reading screen width from the driver properly. I don't know anything about the APIs or standards involved, but if it's as simple a fix as changing a value in memory..? It's not a permanent one, the memory layout changes every time so it's inconvenient to do every time to say the least.
This happens in the nightly builds as well as the latest stable. The tablet is a Huion 580, which is basically a generic model. I'd assume the same thing happens on Monoprice tablets as well as many others since they all use interchangeable drivers. |
I have two monitors on a PC running Windows 7 x64. My primary on the right, secondary to the left of it. I set my driver to only use a single screen for input (monitor 1, 1920x1080). When using Inkscape, the input is offset, varying depending on what the resolution the secondary monitor is set to.
I actually managed to "fix" it. I opened up a memory editor, searched for the combined length of both monitors (3200 if the secondary is 1280) and changed it to 1920. After doing that, the tablet worked perfectly.
Inkscape doesn't seem to be reading screen width from the driver properly. I don't know anything about the APIs or standards involved, but if it's as simple a fix as changing a value in memory..? It's not a permanent one, the memory layout changes every time so it's inconvenient to do every time to say the least.
This happens in the nightly builds as well as the latest stable. The tablet is a Huion 580, which is basically a generic model. I'd assume the same thing happens on Monoprice tablets as well as many others since they all use interchangeable drivers. |
|
| 2013-06-06 14:23:19 |
Dean Lillie |
description |
I have two monitors on a PC running Windows 7 x64. My primary on the right, secondary to the left of it. I set my driver to only use a single screen for input (monitor 1, 1920x1080). When using Inkscape, the input is offset, varying depending on what the resolution the secondary monitor is set to.
I actually managed to "fix" it. I opened up a memory editor, searched for the combined length of both monitors (3200 if the secondary is 1280) and changed it to 1920. After doing that, the tablet worked perfectly.
Inkscape doesn't seem to be reading screen width from the driver properly. I don't know anything about the APIs or standards involved, but if it's as simple a fix as changing a value in memory..? It's not a permanent one, the memory layout changes every time so it's inconvenient to do every time to say the least.
This happens in the nightly builds as well as the latest stable. The tablet is a Huion 580, which is basically a generic model. I'd assume the same thing happens on Monoprice tablets as well as many others since they all use interchangeable drivers. |
I have two monitors on a PC running Windows 7 x64. My primary on the right, secondary to the left of it. I set my driver to only use a single screen for input (monitor 1, 1920x1080). When using Inkscape, the input is offset, varying depending on what resolution the secondary monitor is set to.
I actually managed to "fix" it. I opened up a memory editor, searched for the combined length of both monitors (3200 if the secondary is 1280) and changed it to 1920. After doing that, the tablet worked perfectly.
Inkscape doesn't seem to be reading screen width from the driver properly. I don't know anything about the APIs or standards involved, but if it's as simple a fix as changing a value in memory..? It's not a permanent one, the memory layout changes every time so it's inconvenient to do every time to say the least.
This happens in the nightly builds as well as the latest stable. The tablet is a Huion 580, which is basically a generic model. I'd assume the same thing happens on Monoprice tablets as well as many others since they all use interchangeable drivers. |
|
| 2013-06-06 14:24:14 |
Dean Lillie |
description |
I have two monitors on a PC running Windows 7 x64. My primary on the right, secondary to the left of it. I set my driver to only use a single screen for input (monitor 1, 1920x1080). When using Inkscape, the input is offset, varying depending on what resolution the secondary monitor is set to.
I actually managed to "fix" it. I opened up a memory editor, searched for the combined length of both monitors (3200 if the secondary is 1280) and changed it to 1920. After doing that, the tablet worked perfectly.
Inkscape doesn't seem to be reading screen width from the driver properly. I don't know anything about the APIs or standards involved, but if it's as simple a fix as changing a value in memory..? It's not a permanent one, the memory layout changes every time so it's inconvenient to do every time to say the least.
This happens in the nightly builds as well as the latest stable. The tablet is a Huion 580, which is basically a generic model. I'd assume the same thing happens on Monoprice tablets as well as many others since they all use interchangeable drivers. |
I have two monitors on a PC running Windows 7 x64. My primary on the right, secondary to the left of it. I set my driver to only use a single screen for input (monitor 1, 1920x1080). When using Inkscape, the input is offset, varying depending on what resolution the secondary monitor is set to.
I actually managed to "fix" it. I opened up a memory editor, searched for the combined length of both monitors (3200 if the secondary is 1280) and changed it to 1920. After doing that, the tablet worked perfectly.
Inkscape doesn't seem to be reading screen width from the driver properly. I don't know anything about the APIs or standards involved, but if it's as simple a fix as changing a value in memory..? It's far from a permanent or practical fix, the memory layout changes every time so it's inconvenient to do every time to say the least.
This happens in the nightly builds as well as the latest stable. The tablet is a Huion 580, which is basically a generic model. I'd assume the same thing happens on Monoprice tablets as well as many others since they all use interchangeable drivers. |
|
| 2013-06-06 14:26:11 |
Dean Lillie |
description |
I have two monitors on a PC running Windows 7 x64. My primary on the right, secondary to the left of it. I set my driver to only use a single screen for input (monitor 1, 1920x1080). When using Inkscape, the input is offset, varying depending on what resolution the secondary monitor is set to.
I actually managed to "fix" it. I opened up a memory editor, searched for the combined length of both monitors (3200 if the secondary is 1280) and changed it to 1920. After doing that, the tablet worked perfectly.
Inkscape doesn't seem to be reading screen width from the driver properly. I don't know anything about the APIs or standards involved, but if it's as simple a fix as changing a value in memory..? It's far from a permanent or practical fix, the memory layout changes every time so it's inconvenient to do every time to say the least.
This happens in the nightly builds as well as the latest stable. The tablet is a Huion 580, which is basically a generic model. I'd assume the same thing happens on Monoprice tablets as well as many others since they all use interchangeable drivers. |
I have two monitors on a PC running Windows 7 x64. My primary on the right, secondary to the left of it. I set my driver to only use a single screen for input (monitor 1, 1920x1080). When using Inkscape, the input is offset, varying depending on what resolution the secondary monitor is set to.
I actually managed to "fix" it. I opened up a memory editor, searched for the combined length of both monitors (3200 if the secondary is 1280) and changed it to 1920. After doing that, the tablet worked perfectly.
Inkscape doesn't seem to be reading screen width (edit: make that height as well) from the driver properly. I don't know anything about the APIs or standards involved, but if it's as simple a fix as changing a value in memory..? It's far from a permanent or practical fix, the memory layout changes every time so it's inconvenient to do every time to say the least.
This happens in the nightly builds as well as the latest stable. The tablet is a Huion 580, which is basically a generic model. I'd assume the same thing happens on Monoprice tablets as well as many others since they all use interchangeable drivers. |
|
| 2013-06-06 14:27:16 |
Dean Lillie |
description |
I have two monitors on a PC running Windows 7 x64. My primary on the right, secondary to the left of it. I set my driver to only use a single screen for input (monitor 1, 1920x1080). When using Inkscape, the input is offset, varying depending on what resolution the secondary monitor is set to.
I actually managed to "fix" it. I opened up a memory editor, searched for the combined length of both monitors (3200 if the secondary is 1280) and changed it to 1920. After doing that, the tablet worked perfectly.
Inkscape doesn't seem to be reading screen width (edit: make that height as well) from the driver properly. I don't know anything about the APIs or standards involved, but if it's as simple a fix as changing a value in memory..? It's far from a permanent or practical fix, the memory layout changes every time so it's inconvenient to do every time to say the least.
This happens in the nightly builds as well as the latest stable. The tablet is a Huion 580, which is basically a generic model. I'd assume the same thing happens on Monoprice tablets as well as many others since they all use interchangeable drivers. |
I have two monitors on a PC running Windows 7 x64. My primary on the right, secondary to the left of it. I set my driver to only use a single screen for input (monitor 1, 1920x1080). When using Inkscape, the input is offset, varying depending on what resolution the secondary monitor is set to.
I actually managed to "fix" it. I opened up a memory editor, hooked it to inkscape and searched for the combined length of both monitors (3200 if the secondary is 1280) and changed it to 1920. After doing that, the tablet worked perfectly.
Inkscape doesn't seem to be reading screen width (edit: make that height as well) from the driver properly. I don't know anything about the APIs or standards involved, but if it's as simple a fix as changing a value in memory..? It's far from a permanent or practical fix, the memory layout changes every time so it's inconvenient to do every time to say the least.
This happens in the nightly builds as well as the latest stable. The tablet is a Huion 580, which is basically a generic model. I'd assume the same thing happens on Monoprice tablets as well as many others since they all use interchangeable drivers. |
|
| 2013-06-06 15:05:53 |
su_v |
tags |
input tablet |
tablet win32 |
|
| 2018-08-09 06:16:46 |
Jasper |
bug |
|
|
added subscriber Jasper |
| 2021-09-01 06:20:24 |
Carsten Pietzsch |
bug |
|
|
added subscriber Carsten Pietzsch |
| 2021-09-10 05:51:09 |
Mike Cline |
attachment added |
|
Animated GIF showing tablet offset problem. https://bugs.launchpad.net/inkscape/+bug/1188211/+attachment/5524266/+files/TabletOffset.gif |
|
| 2022-05-30 06:59:02 |
Christian Zommerfelds |
bug |
|
|
added subscriber Christian Zommerfelds |
| 2022-05-30 07:02:56 |
Christian Zommerfelds |
bug watch added |
|
https://gitlab.com/inkscape/inkscape/-/issues/1892 |
|
