Event naming redux

I know that we’ve kicked this can down the road for many iterations, but the newly posted “Hello, World!” examples on YouTube once again demonstrate that what we “think” versus what the events are called don’t align.

For example: https://youtu.be/y_2GKoOkayo?si=_8yBiY56XhDR2tJ7&t=29

The voice over calls out the event as “the user’s Click action”, but the event is called “Pressed”. This is a quite exact example of where these changes made in API 2 are failing.

1 Like

Do you want the voice over to be changed or the Pressed event be renamed?

I want the Action event back! :wink:

Also, yuck, that sounds like an AI voice if you ask me :-1:. It doesn’t sound like anyone we know and the inflections are wrong.

It’s not that I’m asking for a change in the videos; my point here is that after all of this time (what’s it been 7-ish years?), even the Xojo team still think in the old manner. This was hashed out ad nauseum back in the API 1.0 to 2.0 change cycle, and this is just one example of the change being “odd” and even unnecessary as was discussed back then.

I’m in full agreement with @Tim_Parnell - the Action event was the best descriptive name for this even. And I also hate robo-voice. Granted, this one is better than many before, but it’s still uncomfortable to listen to since it’s just that little bit “off”. At least they didn’t choose the gratuitous GB or Aussie accent.