getting keyboard to come up when straying from default settings

[kylebakerio]

https://web2vr-demo.glitch.me/where-is-keyboard.html https://glitch.com/edit/#!/web2vr-demo?path=where-is-keyboard.html%3A89%3A7

In this relatively basic riff on the examples I'm playing with, I'm using these options:

{ 
              parentSelector: "#anchor", 
              position: { x: 0, y: 1.5, z: 0 },
              debug: false, 
              skybox: false,
              createControllers: false,
            }

No keyboard comes up that I can see anymore when I click on a text box. How can I get the keyboard back, and tell it where to be positioned?

[kylebakerio]

found it, keyboard is getting placed with a negative y value, underground. Bug, needs to have a way to set keyboard position. Default should probably be placed relative to the web2vr panel that is created? See example linked above. I looked at source, looks like that should be happening already actually, not sure why it breaks here.

[kylebakerio]

Unfortunately, even if I position the keyboard myself (which also isn't working quite right), the keys aren't clickable, it seems. super-keyboard requires that you register the selector of your controller with it, but I don't see where I can do that... document.querySelector('[super-keyboard]').setAttribute('super-keyboard','hand','#right-hand') and document.querySelector('#vr-keyboard').setAttribute('super-keyboard','hand','#right-hand') both seem to fail. :/

I also tried looking at the ID of your built-in controllers, which is the example mentioned in the super-keyboard repo, #rightHand it seems, but just adding the same selector to my controllers also didn't work for me, which really surprised me. It's important, because the controllers injected by this app are naive and are put in the world, not attached to the camera rig, and so are incompatible with, for example, movement-controls in aframe-extras.

It would be nice if this repo didn't come bundled with physics and super hands and built-in controllers and so on, which are extra bloat I won't be using in my app. The library seems to assume one will build their app around this library, instead of being a single-focus library that's easy to add in to other contexts.

Don't get me wrong, I love the idea of including examples that illustrate this library working with those libraries. I just want to have control over that integration myself.

[kylebakerio]

I later resolved issues getting keyboard to show up properly: https://glitch.com/edit/#!/web2vr-demo?path=index.html%3A31%3A0