View Single Post
Posts: 456 | Thanked: 1,580 times | Joined on Dec 2009
#36
A brief update:

So, it turned out that most of the "hack" I prepared was not necessary,
To 99.5%, my current solution for adjusting the touch input to different resolutions boils down to properly using the existing configuration options.
The remaining bit is a small change to work around an hard-coded upper limit:
Code:
diff --git a/src/base/touchinputdevice.cpp b/src/base/touchinputdevice.cpp
index 3b7cd0b..9d0cffd 100644
--- a/src/base/touchinputdevice.cpp
+++ b/src/base/touchinputdevice.cpp
@@ -324,7 +324,7 @@ void TouchInputDevice::setGridVisible(bool on)
 
 void TouchInputDevice::setDpadAreaSize(int size)
 {
-       int rSize = qBound(160, size, 320);
+       int rSize = qBound(160, size, 16384);
        if (m_areaSize != rSize) {
                m_areaSize = rSize;
                setDpadAreaDiagonalSize(m_diagonalAreaSize);
The diff is against 4f40a85b141e402b7c302fe31159c15c2467161d of my github repository.
This is the suggested commit if you want to play with the "current stable" Emumaster version.
From later commits on, I introduced more experimental changes.

In order to adjust the touch input display to your screen resolution, you have to edit the file: ~/.config/elemental/emumaster.conf

For SailfishOS running on an 1920x1080 resolution, I use the following settings:
Code:
[General]
touchAreaDiagonalSize=128
touchAreaSize=512
I uploaded version emumaster-0.3.1-10.82.1.jolla.armv7hl.rpm to my Mer repository.
I hope that this version plus the information in this thread fixes most issues for you and I am very much looking forward to your feedback.
__________________
 

The Following 7 Users Say Thank You to Wonko For This Useful Post: