Or.. some users are not that sensitive...
I had an old file with a Pflow setup that I needed to revisit in 2018. Loaded up in 2018 and realized the same double-click issue is bugging PFlow as well. Keep in mind every change to a node takes 2 minutes or more to update the flow.
Here's what happens:
- I click on a checkbox > nothing happens
- I need to click twice > OK, lesson learned
- I then switch the node, think it's not in focus, so I click twice
- I now realize the node already was focused and registered both clicks
- Flow updates for 2 minute, then registers the second click, updates again for 2 minutes
- I now click a third time to get my change to update, 2 more minutes of waiting
The result is I waited 6 minutes instead of 2 to get the result I wanted. IF you have to wait 15 minutes instead of 5 on a more complicated pflow once you accidentally hit a button twice and it quickly gets to a point where your software is not usable.
That's not being sensitive, it's about common sense in how software works everywhere else. If you don't see it... you may have a blind spot.
Back to topic - Max team starts work on a massive UI update, they deliver good work but stop even though it's not finished, causing users to complain. They realize they need to react and think they may solve it. Great, but they wasted 2 years, and it will probably take another 2 to iron out bugs that should've been fixed in the first place when things were hot. I guess a cynic could call that... long-time commitment.