Portrait-Click Issue

[Nickademus]

When a player clicks on their character's portrait to open the character sheet (5e ruleset, but should affect most of them), it triggers the User.onIdentityStateChange event is if the player changed characters to their current one. Is this intended behavior? It makes it hard to judge when the player is opening their character sheet or legitimately swapping characters.

[Moon Wizard]

This has been the behavior for several years. if controlling more than in character, single click to switch active characters, and double click to open the character sheet.

Regards,
JPG

[Nickademus]

What I am saying is that double clicking to open the character sheet triggers the onIdentityStateChange event with a statename of 'current' as if the player switched characters. The double click is also registering a single click. Seems to me like it should be either-or.

[Moon Wizard]

The FG client doesn't provide that layer of granularity. A double click is simply a second click within a short period of time.

Regards,
JPG

[Bidmaron]

MW , if I understand Nickademus correctly, he is wondering why the opening of an active character sheet would cause a change pc event. The event should fire only when the Pc changes not when you open active character sheet. That's what I think he is getting at

[Nickademus]

The event is said to fire when the character's name is changed, the die color is changed, or when a new character is chosen. Simply clicking once on the current character shouldn't logically fire the event. That meets none of the situations the occurrences is trying to communicate.

[Moon Wizard]

I understand what both of you are saying. I'm just providing information on how it works currently.

In FG, a double click fires a click event on the first click, and a double click event on the second click.

In CoreRPG (and rulesets going back for years), when controlling multiple PCs as a player, the first click event makes that PC active, and the double click event opens the character.

If you're looking for something different, then the code would need to be modified via an extension to do something different with the click events.

Regards,
JPG

[Nickademus]

Okay, so it is intended behavior. Thank you.