How to tell if a session is the designer in Perspective

In Vision I could look at the SystemFlags and tell if I was in a designer session or a client session.

Is there a similar way to determine this in Perspective.

The reason I ask is I want to toggle visibility conditionally on a label depending on if the perspective session is running in the designer or not.

Thanks,
Brandon

Do you mean like the session prop device/type?

image

Yeah! I think that would be exactly what I want

EDIT: Does anyone know why my designer right now says browser and not designer?

Bump, I have this same issue. Designer says "browser".

What version are you using?

8.1.20

According to the opened issue, this is a result of the Designer incorrectly handling a Gateway restart. To prevent this:

  • Close all Designers before restarting your Gateway.
  • Close and re-open your Designer if it was open during a Gateway restart.

Issue for reference: IGN-6238.

1 Like

@cmallonee, this also happens without a gateway restart. I just observed it happen on Designer reconnect after being offline for a while due to VPN disconnection. session.device.type showed designer (correct) until the Designer reconnected to gateway, and then switched to browser (incorrect). Gateway hasn't been restarted for a month:
image
Designer was online yesterday. This doesn't seem to happen on all brief connection losses, but does happen enough to be annoying--especially when working with multiple Designers open that all need a restart to correct this.

I am a similar issue where clients show a device type of 'designer'. Any update on a fix?

No, there is no estimated time to begin work on this fix.

Any updates on this? Just started having this same issue. We use it quite a bit to see objects that are normally invisible for placement etc.

1 Like

Also seeing this issue. It's helpful for preventing pushing session-based info. For example, I want a view defaulted to some values, but it keeps using my browser session information. If we can reliably check if it's the designer, we can keep those default values in place. Hopefully this can be fixed in the next ignition version.