Not sure if it is my browser or the game, but on the third slide, I'm not sure if it is interference with the browser or if there is no focus on the game to allow me to grab and move objects. (I'm using a rather current version of Chrome. I can interact with some objects with a single click. I double click and the "Prototype Studio" text in the Unity WebGL frame is grabbed.)
Is there a way to probably use something like user-select:none to prevent the frame's contents from being selected when double-clicking?
Thanks for your feedback! The doubleclick represents the "doubletap" action on Instagram, the way users "like" posts in their feed. I wanted to create a sense of intent for players to acknowledge the photos the way they might while browsing social media.
I have noticed that the HTML build is a little buggy with the click-and-drag object interactions. It's inconsistent for me, so it's been hard to reproduce. Sometimes restarting the page helps, it seems. I may poke around to see if I can find a way to make that interaction more predictable in the web build.
← Return to game
Comments
Log in with itch.io to leave a comment.
Why doubleclick instead of single click?
Not sure if it is my browser or the game, but on the third slide, I'm not sure if it is interference with the browser or if there is no focus on the game to allow me to grab and move objects. (I'm using a rather current version of Chrome. I can interact with some objects with a single click. I double click and the "Prototype Studio" text in the Unity WebGL frame is grabbed.)
Is there a way to probably use something like user-select:none to prevent the frame's contents from being selected when double-clicking?
Thanks for your feedback! The doubleclick represents the "doubletap" action on Instagram, the way users "like" posts in their feed. I wanted to create a sense of intent for players to acknowledge the photos the way they might while browsing social media.
I have noticed that the HTML build is a little buggy with the click-and-drag object interactions. It's inconsistent for me, so it's been hard to reproduce. Sometimes restarting the page helps, it seems. I may poke around to see if I can find a way to make that interaction more predictable in the web build.