Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhance Touch Anywhere and Range of Motion steps for multiple taps and touches #1482

Open
wants to merge 13 commits into
base: main
Choose a base branch
from

Conversation

davwillev
Copy link
Contributor

This PR primarily enhances the existing Touch Anywhere step so that it can be configured to multiple taps (e.g. double-taps) and touches (e.g. 2 fingers).

Having tested a version of the range of motion tasks extensively over the past few years, we have seen many occasions where a participant will inadvertantly touch the screen when placing the phone onto their body ready for a measure. At other times, we would see a recording ruined by an accidental tap mid-task. At best, these problems result in useless data. After trying various different instructions, we realised that the best solution was to utilise a double-tap or a two-fingered tap (or even a combination of both) to start (and end) the test.

To enable this enhancement, I have added two new parameters to the touchAnywhereStep ('numberOfTaps' and 'numberOfTouches'). This means that any task implementing this step will also need either a constant set for each of these, or additional parameters enabling the user to set the tasks dynamically. Currently, the touchAnywhereStep is only implemented within the range of motion tasks within RK. I have therefore added two new parameters to the range of motion step (and knee and shoulder tasks) and reproduced the functionality for multiple taps/touches in these too.

Finally, I have also configured dynamic instructions that enable researchers and developers to set different numbers of taps and touches, and appropriate instructions will automatically be produced and displayed/spoken. To make these dynamic instructions available to every implementation of the rangeOfMotion step required one additional parameter, 'instructionText' (which now mirrors the touchAnywhereStep in this way).

These changes been very successful during testing and I hope they will be of use to others.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant