Tweet
I use a Wacom tablet (Intuos3 pen+mouse) and have been switching between that and a regular mouse when using eSignal.
In Windows7 the Wacom mouse acts like a normal mouse in every way. As soon as it travels over an open eSignal window it behaves like the Wacom pen (each coordinate on the tablet is a specific location on the screens).
This would be somewhat workable, except that the Windows mouse cursor still tracks like a mouse, but the clicks respond in eSignal based on the physical location of the mouse on the tablet (as if its the pen). I finally figured out what was going on after a lot of clicking to test the relative location.
**The 'main' monitor w/ the Start Menu is the far left. The location of the cursor vs the location of the "click" suggests that eSignal maps each individual monitor worth of windows to the full 7680px of the span instead of the 2560px it actually is, and the height as the full span's height instead of just 1600px.**
Also, I recently installed Win7 clean. I had eSignal open when the Wacom driver finished installing, and it worked properly until I restarted eSignal (not Windows--the OS was left running). The restart of eSignal reverted it back to the mismatch when using the mouse. So now I'm not sure how to pinpoint the issue (wacom drivers? graphics card drivers? esignal? some interaction between them? Thunderbolt port monitor mis-representation? etc).
It does the same thing on a macbook pro 17" with 2x27" monitors+the 17" built-in and mac pro--bootcamp. I don't have a dedicated trading PC built yet, but then I'd just use a regular mouse+the 3DConnexion navigation setup anyway.
Ideas? Help?
Thanks much!
**Edit--Windows clearly knows where the cursor is, but eSignal has its own mapping ideas. If I am clicking in a monitor to the right in another program, it works properly in the program, but also clicks in eSignal in the monitor to the left and steals focus. Hovering over things in eSignal makes the hotspots/highlighting react normally to the correct cursor location (such as in the Research panel), but then actually clicking responds over the left with the weird mapping.**
In Windows7 the Wacom mouse acts like a normal mouse in every way. As soon as it travels over an open eSignal window it behaves like the Wacom pen (each coordinate on the tablet is a specific location on the screens).
This would be somewhat workable, except that the Windows mouse cursor still tracks like a mouse, but the clicks respond in eSignal based on the physical location of the mouse on the tablet (as if its the pen). I finally figured out what was going on after a lot of clicking to test the relative location.
**The 'main' monitor w/ the Start Menu is the far left. The location of the cursor vs the location of the "click" suggests that eSignal maps each individual monitor worth of windows to the full 7680px of the span instead of the 2560px it actually is, and the height as the full span's height instead of just 1600px.**
Also, I recently installed Win7 clean. I had eSignal open when the Wacom driver finished installing, and it worked properly until I restarted eSignal (not Windows--the OS was left running). The restart of eSignal reverted it back to the mismatch when using the mouse. So now I'm not sure how to pinpoint the issue (wacom drivers? graphics card drivers? esignal? some interaction between them? Thunderbolt port monitor mis-representation? etc).
It does the same thing on a macbook pro 17" with 2x27" monitors+the 17" built-in and mac pro--bootcamp. I don't have a dedicated trading PC built yet, but then I'd just use a regular mouse+the 3DConnexion navigation setup anyway.
Ideas? Help?
Thanks much!
**Edit--Windows clearly knows where the cursor is, but eSignal has its own mapping ideas. If I am clicking in a monitor to the right in another program, it works properly in the program, but also clicks in eSignal in the monitor to the left and steals focus. Hovering over things in eSignal makes the hotspots/highlighting react normally to the correct cursor location (such as in the Research panel), but then actually clicking responds over the left with the weird mapping.**
Comment