Generally I’ve run into a lack of documentation around the experimental web control UI element. I’m hoping someone has some tips for working with it and interacting in turn with the game. For instance:
- What is the best way to pass events back and fourth? Can this work directly via JavaScript on a rendered page in the element or do I need to set up something like an instance of node.js running alongside with some named pipes or shared memory going back to a c++ helper class?
- If I cover the entire screen with a mostly transparent
canvaselement within the web control, how do I delegate which mouse events and such get passed back to the game and which ones get stopped in the web control? Would stopping the bubbling of the event in the page (like you would normally do to stop events from bubbling up from adivorcanvasto thedocumentorwindowlevels) do it or should the page capture all mouse/keyboard info and send it back to the game? - Any other things of note with the web control? Are there current known issues with it I should look out for or anything that is an issue and won’t be fixed I need to be designing around? Is it safe to treat the UI like a normal web page and just assume that when my game is wrapped up in a year or so the web control will be complete?
Having a lot of fun with UE4 thus far, aside from UI it’s a breeze.