Bachelor Thesis - Computer Graphics Group

More documents

Recommendations

Info

SendInput function had to be used to emulate the mouse click. The effect is the same as if a real mouse button was clicked. Windows sends a correct message to the underlying window for us. Uninitialized Idle Ignored GesturePending GestureActive GestureBroken Cancelled Terminated Figure 4.2: State transitions Without event filtering, inactive windows are normally activated when clicked on, immediately after the button has been pressed, not when it was released. Nevertheless, since the window does not receive the button down message, it is not activated automatically. It has to be done in code by calling SetForegroundWindow. Furthermore, SetCapture must be used in order to receive mouse movement events when the cursor moves over to another window. Theoretically, this should not be necessary. The hook callback function should be called for the other window. And the library state is globally shared. However, in reality, the gesture only worked in the original window, no mouse messages have been received from the outside. As already mentioned, all program instances have their own address space. In order to invoke a callback function in the main application, the code flow has to switch the address space of the main application, where the callback function resides. To achieve this, message passing is used. The initialize function spawns a new so-called message thread running in our process. This thread creates a hidden message-only window receiving standard window messages. 26
The function supposed to invoke the gesture-event or window-ignored callback checks whether the current thread is the message thread. If not, the code is being executed in context of a foreign process. By sending a message to the hidden window, the context switches to our application, where the message is handled. Now the same function is dispatched, but now running in the correct context and thus it is able to call the callback function this time directly. The timeout feature is implemented using a timer. There are two types of timers in Windows, standard and multimedia. Standard timers have been tried first. The main advantage of the multimedia timer [22] being more accurate is not required. However, problems have been experienced with standard timer behavior, while the multimedia one worked correctly. Hence, this type of timer has been selected. The code setting and clearing the timer has to be executed in the context of the main application. Therefore, a timer handler routine is called just before the gesture-event callback function. We have to use a single shot timer to prevent multiple invocations of the handler function. The timer is started on the GestureBegin event, restarted on every GestureMove event a finally destroyed on all other events. If the timer handler procedure happens to be executed, the timeout interval has been reached. A GestureCancel event is sent to the main application. 4.5 Issues experienced The development of the gesture capture library proved a challenge as predicted in the Introduction. Some parts of the actual implementation had to be revised a few times, to solve some problems, which have been discovered only when the fully functional application started to be used practically. The experienced issues include: • some kinds of windows are problematic, such as the Start menu. These have to be detected reliably and ignored automatically. It is not an easy task though, window classes and styles have to be checked. The detection has to be as accurate as possible. Otherwise, windows that use a non-typical combination of attributes may be accidentally ignored • useless mouse movement events are being reported in some cases. In some cases, the mouse-hook callback is being called periodically, even if the mouse cursor does not move, reporting the same cursor position. The last position has to be saved and compared with the “new” position every time, to avoid reporting fake events to the main application • to support mouse button swapping correctly, logical and physical buttons had to be distinguished. The logical button identifiers, reported to the mouse-hook callback function are swapped. However, the physical 27
Page 1 and 2: Charles University in Prague Facult
Page 3 and 4: Contents 1 Introduction 6 1.1 Motiv
Page 5 and 6: Title: Mouse Gestures Author: Milan
Page 7 and 8: 1.2 Existing solution Still, one su
Page 9 and 10: Right clicking the icon will displa
Page 11 and 12: Chapter 2 Gesture recognition Our m
Page 13 and 14: vector of fixed length, called the
Page 15 and 16: measure, we get K nearest objects.
Page 17 and 18: 3.2 Graphical user interface toolki
Page 19 and 20: • QObject instances are organized
Page 21 and 22: 1. the most naive idea is the user
Page 23 and 24: e supported too • the user must b
Page 25: Global uniqueness of the statically
Page 29 and 30: Chapter 5 Main application 5.1 Appl
Page 31 and 32: The gesture capture library identif
Page 33 and 34: is given the opportunity to perform
Page 35 and 36: shape of the gesture. It can also c
Page 37 and 38: 5.7 User interface Universal Gestur
Page 39 and 40: Figure 5.6: Pattern Editor window T
Page 41 and 42: steps would have to be taken: 1. mo
Page 43 and 44: tion can be exploited in some parts
Page 45 and 46: menu. One of the main goals was mod
Page 47 and 48: [13] FireGestures, http://www.xulde
Page 49: Appendix A User documentation 49

Bachelor Thesis - Computer Graphics Group

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?