5E - Single Click Action

[fxg42]

very nice job!

Thank you kindly!

[SirMotte]

Wonderful, the older folks at my table will love it!

[fxg42]

Wonderful, the older folks at my table will love it!

lol! I feel seen

[bratch9]

Looks good, just done a quick check.

Can you apply this to the 'droped' down buttons on the spells as well ? (spell.jpg)

Thanks, my group have this problem all the time, so will be using it this weekend.

[fxg42]

Can you apply this to the 'droped' down buttons on the spells as well ? (spell.jpg)

Hi! That's a good idea. I forgot those!

[MrDDT]

I'm having issues with this working with my other exts. Anyone else having issues? It simply just doesn't do anything. I'm wondering if maybe I need to change the load order or something.

[Weissrolf]

Nice workaround for a common problem that ideally should be solved on an application level.

Unfortunately it doesn't seem to do anything in combination with my other extensions, double clicking action buttons still applies the button action twice. Will test this further.

You're completely correct in that the actual issue is the "sometimes I should double-click, sometimes I should single-click" and there is certainly a better solution to that than disabling double-click Thanks again!

Like an option for users to choose between double- or single-click and then keep it consistent for all buttons.

[nephranka]

I'm having issues with this working with my other exts. Anyone else having issues? It simply just doesn't do anything. I'm wondering if maybe I need to change the load order or something.

The dbl click needs to be fast else it will not be seen by this ext as a true dbl click. I tested on its own and it was working. When I tried this ext with 5E Extension - Combat Automation v1.1 by Xelab\nAutomates Spellcasting and Weapon Attacks. They seem to be in conflict and it was not working no matter how fast I dbl clicked.

[bmos]

I posted a pull request that contains a potential fix for this incompatibility.

I haven't tested to make sure it's working though, so I'm just just a 'armchair contributor' here

[fxg42]

I posted a pull request that contains a potential fix for this incompatibility.

Thank you so much! Can't wait to try out the PR