E-Prime 3 and Windows 10 Tablets

[Christopher Draheim]

Hi all,

A collaborator recently decided that Windows 10 tablets would be easier to use in the field than laptops.

I have not yet used E-Prime 3 and have no access to a tablet, as our lab is still on E-Prime 2 and standard PCs.

My question is how much is involved in adapting tasks that heavily rely on collecting responses from mouse clicks to be tablet compatible?

An old thread I found suggested that the mouse input device is the same as the touchpad on a tablet, however our IT guy said they were separate in E-Prime 3. Also when trying to use an E-Prime 3 task on one of the tablets, our collaborator received the following error:

Any and all help is appreciated!

Thanks,

[Christopher Draheim]

Also, by touchpad I meant touchscreen. Sorry about that.

[Michiel S-Spape]

Hi,

Starting from the bottom. I can tell you (and probably did write in the old thread) that they are, more or less, treated equally. That is generally how Windows, particularly in applications that are not “Store”-apps (i.e. rewritten specifically for Windows 8+), with a few differences. For example, a click and a right-click are used as a “tap” and a long-touch respectively, and I can suspect this could be important for E-Prime 3 RTs based on touch. I am also not too sure what would happen if you were to use both Mouse input responses and touch input responses, but I would expect this to be the same as having two keyboards or two mice attached – both keyboards will work, but you will get only one pointer.

 

That said, adapting the task to E-Prime 3 is generally made easier, because in EP3 you will no longer need the HitState stuff to create buttons. In E-Prime 3 you just add buttons to a slide, and job sorted. Of course, if your code is designed around the idea that a mouse cursor *was* outside an area and then went into an area, that will no longer work with touch: a mouse-pointer moves, but unless somebody slides their finger, a tablet input just gets the coordinate of the press. All in all, I would say that there might be some work in adapting the task, but that is mainly because E-Prime 2 made things difficult when it came to mouse input, and people coded their way around it in idiosyncratic ways.

Best,

Michiel

--
You received this message because you are subscribed to the Google Groups "E-Prime" group.
To unsubscribe from this group and stop receiving emails from it, send an email to e-prime+u...@googlegroups.com.
To post to this group, send email to e-p...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/e-prime/c8b80d97-6a60-42b9-81bc-3b83be849cb2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Christopher Draheim]

Thanks for the information! Though it turns out I just needed to emulate the mouse in the device settings (I was not aware of this), and it seems to work fine now on the tablets, even with the old E-Prime 2 coding for HitStates.