This session property that begins as designer when Designer is first opened changes to browser at some point.
It may have to do with connection loss and reconnect between Designer and Gateway. I noticed this when scripting startup actions to hide components EXCEPT in Designer where we want to see them for configuration. When this session property changes incorrectly to browser, closing Designer and reopening gets us back to correct designer property.
Interestingly the gateway Perspective sessions page also switches these Designer sessions to display as chrome browser sessions when this happens. Two of these are actually Designer sessions:
Note that this doesn’t just affect the Designer, we’ve seen in 8.1.14 that it is affecting clients as well, where clients are reporting in session.props.device.type as designer instead of browser. I’ve reported this to IA support already
Want to add that i also experience the same, but the other way around.
Perspective web browser clients with a session property as designer. Its not often, but it has happened a few times now.
Objects that should be visible “if X or designer”, are all showing in the webbrowser even though X is false. The session scope on the gateway shows up as designer. But there is no designers open.
Its a bit concerning, as it gives the operator false information.
Just had a customer call because he could see some objects he was not supposed to see. I have a few objects with an expression binding on the visible property:
{tag}||({session.props.device.type}='designer')
This was suggested from support a few years ago, so the objects would not disappear from the designer when visible is false.
Not exactly sure how often i have seen this now, but it has to be 5-10 times i have seen a browser client show up with a designer session scope, under status→connections→perspective sessions.
Hi ,
we have upgraded our project from version 8.1.49 to 8.3.3
After that when we open the project in designer (from a terminal server) it shows device type browser . now we have code that is dependant on device type not being designer and this has caused issues. any idea why this happens?
I was hoping it would have been fixed in the big 8.3 update but there is still a lot of issues with session variables being overwritten by project saves in 8.3.4. Plus the gateway showing the 8-digit ID whereas the designer itself showing the 32-digit ID (for the same session).
I also don't understand why the gateway even lists the session as a "browser" when it shows the ID type I believe is unique to designers. Unless I'm mistaken on how the IDs are classified? The device is also not correct, it is Windows 11 not 10.
