I have done the following in testing omeka everywhere on my windows 10 surface device:
1. Ensure flash player 11 is installed
2. download https://github.com/ideum/omeka-everywhere/blob/master/Table/cs052-omeka-collection-viewer/installer/OmekaCollectionViewer_Installer.exe
3. Configure for my omeka instance as per http://openexhibits.org/wp-content/uploads/documentation/OmekaEverywhereCollectionViewer.pdf
When the viewer opens, I am able to load the default endpoint that comes pre-loaded in the software (I can select the drop down menu for endpoints, but nothing happens when I tap on the items). If I proceed to load the software, I am able to open the browser menu and can scroll through the tags, but nothing happens when I click on most of them. when I am able to load images into the browser view after click on certain tags, they aren't sent to the "stage". I would show screenshots of this but as a new forum user I don't seem to be allowed to (!)
Any suggestions about what to do next or how to troubleshoot further?
It sounds like tap gestures aren't being recognized consistently. Try reducing the tapDuration in the OmekaCollectionViewer.cml value to something like 50 ms to see if that increases the sensitivity. When you click on the thumbnails in the results browser, there will be a visible indicator on the thumb itself indicating it has been successfully selected. If this is not happening, chances are the tap duration setting will resolve it also. If this setting is not the culprit to your issues, please send me a link to your omeka endpoint so I can troubleshoot on my end.
Thanks very much for the response. The tap duration was set to 50ms by default by the looks of it (see my OmekaCollectionViewer.cml file below) I can try reducing it further but the issue I'm encountering doesn't seem to be a global tap setting, I can reliably bring up images when clicking on certain tags but others aren't loading to the browser despite many attempts. I'll post a link to a video when I'm back in the office as it's hard to describe the issue clearly.
Can I confirm that the only software I need to be installing/configuring is the OmekaCollectionViewer? i.e. there isn't some third party thing I need to install (other than flash player)?
<?xml version="1.0" ?>
Collection Viewer Declaration
@param tapDuration: The tap evaluation time(ms) to qualify tap gestures between touch up and down events.
Variable touch response between devices or different versions of Windows, may require
tweaking this value.
@param attractTime: The inactivity time(s) permitted before application enters attract mode
<OmekaCollectionViewer tapDuration="50" attractTime="120">
<!--ui skin options-->
<!--media viewer object pool-->
<Include src="cml/display/viewer/MediaViewer.cml" count="40"/>
<!--query tools: 1(wall mode) or 2(table mode)-->
Just adding that I'm experiencing this issue on the preloaded endpoints - it's not unique to my omeka instance.
I did some more experimentation and found that triple-tapping seemed to work more successfully in sending items to the stage, I discovered this while documenting the issue here:
with that in mind, I had a lot more success in adjusting the tap duration to a higher value on my device (400ms seems to be a sweet spot)
Meanwhile, I realised the 3 tag limit was one reason why I was having difficulty before.
Thanks very much for your assistance Shaun.
I noticed you were attempting to load additional tags when the maximum number of three tags filters were already selected so, even if tap wasn't failing which it seems to be, this wouldn't have worked in that state. When there are three tag filters being applied, you need to explicitly remove some of them in order to add more.
As I said, this seems to be a tap duration issue. My reason for saying that is the tap gesture criteria is simply an evaluation of time between touch_begin to touch_end. If this time is less than or equal to the duration, then a tap event is dispatched. The fact that you were able to triple tap implies a latency may be in effect causing the first two releases to miss their window (remember flash is single threaded). In your case, I feel increasing the duration to 200ms should permit the releases to fall within the time frame.
During development, I realized the touch response varied between Win7 and Win8 which is why I exposed the tap duration setting in the first place. If the adjustment to the duration does not resolve your issue, please tell me which version of Windows you are running and I will attempt to reproduce the issue on my end.
Confirming that making the adjustment to the tap duration setting has resolved my issue.
Thanks again for this.