It’s not easy for me to make the Kindle mouse pointer working with Qt (of course, unofficial). When you press the joystick, it cannot track more than one direction at a time (without diagonal movements), and the screen refreshes too slowly for good feedback.
I have limited acceleration, but with screen latency it is very unpleasant to use. When you release the button to the left, the mouse will move for 1-2 seconds ... and this is not always a constant delay.
Given these limitations, I really need help from the application. I need a method that the mouse driver plugin can use to determine what should be the acceleration profile ... so it can say that it slows down when it crosses the button. An application can help identify regions where different acceleration makes sense (start by shifting one pixel in the drawing area, but start at 10 or so for the dead space of the dialog). More simply, the application should be able to point the mouse pointer to the transition from the cursor to keyboard mode, etc.
However, I can list the mouse drivers, but it seems that I do not need the driver names. They are not QObjects, so there is no qobject_cast. How can I identify them as mine and safely drop them? I can make it quit, but it seems pretty lame.
Am I just assuming plugins are mine and molt them?
I need a simple way to transmit signals / slots.
UPDATE
Perhaps the plugins may somehow notify the application. Perhaps using QApplication :: topLevelWidgets (), trying qobject_cast searches for QMainWindow ... then sending it its own signal with the inner class of the QObject-based plugin handler? Then the application can deploy and configure the connections that he really wanted to deal with. I will try it today or tomorrow.
source
share