PDA

View Full Version : Of buttons and text-fields



Weissrolf
August 27th, 2021, 09:36
Please make "blue" single-click buttons and double-click text-fields more distinguishable from each other. They currently look the same despite needing different number of mouse-clicks. Thanks.

Weissrolf
September 3rd, 2021, 21:52
SW stated that single vs. double click behavior of character sheets is up for the ruleset developers to implement. What is your stance on having single- and double-click buttons mixed, especially on the Action tab? My players get confused about that regularly.

ShadeRaven
September 3rd, 2021, 22:06
To be honest, even I goof that up sometimes.. and some of my players struggle to find the buttons much less know how to use them correctly ;)

Weissrolf
September 8th, 2021, 21:33
With Moon Wizard stating single-click to be the new default. Will the PF2 ruleset follow suit on character sheets?

Moon Wizard
September 8th, 2021, 21:49
I didn't say that the new default is single-click. I just updated the code so that buttons will ignore double-clicks, so that players will not accidentally double roll if they do double click.

Regards,
JPG

Weissrolf
September 8th, 2021, 22:01
Ah yes, I forgot that "buttons" are only those tiny little things in the spells section of the Action tab, while everything big (single or double-clickable) is a "text field". So you only referred to a limited number of UI elements and not all clickable button-like things. Too bad.

So we are back to the original post: is there any chance that the PF2 ruleset might introduce consistent click behavior on clickable UI elements instead of mixing single- and double-click elements right beside each other?

damned
September 9th, 2021, 00:07
If you double click everything now (or soon) you will likely get the consistent approach to all charsheet interactions.

Ckorik
September 9th, 2021, 03:16
This thread feels antagonistic - although with the amount of attention it's already gotten I figured I'd toss out a 'thanks' about the double click - we honestly have never really figured out when it double clicks or single clicks correctly - and lag will frequently get more clicks than intended.

Weissrolf
September 9th, 2021, 08:31
Yes, in v4.1.6, double clicking on buttons is disabled by default, unless enabled by the ruleset/extension code.
The question still stands: will the PF2 ruleset use consistent behavior or mixed behavior in v4.1.6? Personally I would prefer single clicks on everything, but either way is an improvement as long as it isn't mixed.

damned
September 9th, 2021, 08:39
You cant do single clicks on all fields because fields use a single click to become editable.

Weissrolf
September 9th, 2021, 08:55
Which fields are both editable and rollable on a PF2 sheet? I genuinely don't know any except for the singular "Hero Points" field (and double clicking a spell name just posts its name in chat).

v4.16 was just rolled out on my PC and I gave it a quick try. Rollable fields can now be safely double-clicked, but of course there are still fields on PF2 sheets that remain single-click and cannot be double-clicked.

So rolls seem consistent now, albeit superfluously double-click from my perspective, but the sheet as a whole is still a mixed matter. It will be up to the player whether they can compute that mix or start double-clicking on buttons/fields/whatever like Mode/Display and proficiencies now.

Trenloe
September 9th, 2021, 14:32
So rolls seem consistent now, albeit superfluously double-click from my perspective, but the sheet as a whole is still a mixed matter. It will be up to the player whether they can compute that mix or start double-clicking on buttons/fields/whatever like Mode/Display and proficiencies now.
There's one control that's misleading. The weapon damage control. I'll look into changing this to be white, and also add the little dice icon indicating that it is a rollable field, in a future release. Fields that are grey in the standard theme are single click interactions.

The rules of use are (controls colours from the standard PF2 theme):

white number/text fields with a small dice icon = double-click to initiate an action (make a roll or apply an effect)
grey number/text fields/cycler controls = if not read-only, single click to change (one step change in a cycler control, enter edit mode for a number/text control).
Small square buttons = single click to initiate an action (make a roll or apply an effect)

Like I've mentioned, the exception to this is the weapon damage control in the actions tab, I'll change this in a future release.

Weissrolf
September 9th, 2021, 14:46
What is the reason behind keeping only the white fields double-click when everything else is single-click? I suggest to go full in and change them to single-click, too. Then everything is single-click and even protected against accidental double-clicks by Moon Wizard's latest core change.

Trenloe
September 9th, 2021, 14:50
What is the reason behind keeping only the white fields double-click when everything else is single-click? I suggest to go full in and change them to single-click, too. Then everything is single-click and even protected against accidental double-clicks by Moon Wizard's latest core change.
Because that is changing the standard that has been there for many years across a lot of rulesets. If SmiteWorks make a decision to change that standard then the PF2 ruleset will follow.

Weissrolf
September 9th, 2021, 15:17
But Smitework stated that it is up to the ruleset developers to change these standards. So everyone is pointing responsibility away from themselves.

From a relatively new users' point of view (less than 2 years) we don't feel good having to suffer for the rather abstract argument of "no change". Bad design is bad design, it doesn't get better by clinging to it forever.

Trenloe
September 9th, 2021, 15:39
"Bad design" is very subjective. The standard is: double-click on a number/text field to roll, single click to interact with a number/text field, single click to initiate a button - this is not, bad design IMO. I know you think it is, but I disagree with you.

There's a standard that's there, if SmiteWorks wants to change that standard then that's up to them. Closing this thread.