Then I catch the GET request by an HTTP in node set to GET /ui/stage as example.
I'm able to click the area and it switches the tab but times out after a few seconds.
I tried to add a msg.statusCode:200 but that does not help. How can i prevent my browser to search for the not existing /ui/stage page after changeing the tab?
the ui_control node does not really pass messages through.. there are some it sends to the dashboard and some that it receives. Net is that it doesn't pass through the msg.req and msg.res properties from the original message and so the http response node fails. - You can probably just wire them in parallel and send the message to both the ui_control and http response at the same time.
That brings me to a blank page that has the payload as text.
If I delay the second 'direct' connection it first brings me to the correct tab and then after the delay times out it shows a blank page with payload as text.
Do you have a sample how ui control node should be used to switch tabs?
But that's hard-coded to the tab n°. Is there no solution for tab names?
I mean that's what the ui controll tells in the info:
Allows dynamic control of the Dashboard.
The default function is to change the currently displayed tab.
msg.payload should either be an object of the form {"tab":"my_tab_name"},
or just be the tab name or numeric index (from 0) of the tab or link to be
displayed.
Have a look in to my first post the href is without white space. I think I do not need to encode with. Or do you think the href has to be in line with the tab name?
What happens is this: /ui/?tab=whitebox1#!/0?socketid=QF0rfwHp3wnsijNBAABw