search

djipco / webwelder

WebWelder is a TouchDesigner component (.tox) facilitating 2-way communication with a web page using the WebSocket protocol.
Apache License 2.0
22 stars 0 forks source link

about using mobile as the websocket client #2

Open UFeatherSerpent opened 1 year ago

UFeatherSerpent commented 1 year ago

Dear Cote! Thanks for your tox, I have been recently trying to figure out how websocket can be used in TD. And you give me a perfect answer. However, when I follow your instruction, "If you want to test the demo page from a device different than the one running TouchDesigner (such as a mobile device), you will need to point your mobile browser to the IP address of the machine where TouchDesigner is running."

Then, I check the DAT table, I found that the touchzone, body, and the button 1,2 data is not available, while the localhost webpage interface is working normally, any comments on this issue???

Best, UFeatherSerpent

djipco commented 1 year ago

The WebSocket URL also needs to point to the machine running TouchDesigner.

UFeatherSerpent commented 1 year ago
Screenshot 2022-09-29 at 3 45 27 PM

I think i have pointed the WebSocket URL properly, the problem as you can see in the above pics, is that the "touch-zone", "body","button1", "button2" value seems not triggered on the mobile browser, I am using iphone 13Pro, safari and chrome both not sending those 4 data.

Thanks for your prompt reply, Cote!

djipco commented 1 year ago

Sorry for this late response. It seems I missed the notification. I'm not sure what the problem is. It's hard to tell without a little more debugging information...

struvel commented 9 months ago

Bonjour DJIPCO,

Un grand merci pour votre développement de WebWelder. C'est exactement le .tox qu'il me faut pour communiquer avec TD. Ce qui est juste dommage c'est que les boutons ne fonctionnent pas... Y'aurait il une solution ? J'ai essayé de changer des données mais je n'y arrive pas.

Pixario

djipco commented 4 months ago

Sorry for this late response. It seems I missed the notification. I'm not sure what the problem is. It's hard to tell without a little more debugging information...