Replies: 3 comments 7 replies
-
Hi @myrtevos, One possibility is that the buttons aren't yet rendered on the DOM when the webgazer extension is trying to find them. This is a possibility for custom plugins with asynchronous or event-based displays. I'm trying to think about how to create a general purpose solution, but the current code is certainly not general. Can you post the full plugin code? |
Beta Was this translation helpful? Give feedback.
-
Hey @myrtevos, this is now fixed in the code and will be included in 6.3.1. The release will be out in the next day or so. |
Beta Was this translation helpful? Give feedback.
-
Hi, Thanks again for the super quick bug fix on this! However, I'm still struggling a bit. With the code as given above, the bounding rectangle coordinates for the image-buttons are way off. Width and height are both 0, and the left & right / top & bottom coordinates are identical. Getting the coordinates for the parent div helps somewhat, but not completely: the width/height dimensions especially are way too small. After playing around with it for a while and trying different things I wonder if the problem is that jsPsych's CSS (for an array of buttons, which is what I'm coercing my images into) is interfering with my own CSS. I'll try stripping out the whole 'button' part of the plugin to see if that's the case, but since I'd really like to see if I can get what I need out of the Webgazer extension using only/mostly the standard jsPsych plugins, I thought I'd post here and ask for help again. Code is still as given in the thread above. Many thanks in advance! |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all,
I've got a webgazer experiment that an actual programmer built last year by writing and putting together custom jsPsych plugins. This works great, and/but I'm keen to see how the "official" jsPsych plugins compare, so I've been trying to create the same experiment using the new jsPsych webgazer extension. So far so good, but the extension doesn't seem to 'find' my CSS selectors.
Here is the relevant section of the timeline:
(Yes, this is a modified audio-button-response plugin named "Betty", it's a long story)
And here is the relevant section of the plugin:
There's a few CSS classes from bootstrap in there that I think aren't relevant to the problem. Just in case, this is what the CSS class
.trial-content
looks like:Anyone with slightly better (read: any) CSS intuitions who can see where I've gone wrong?
Many thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions