Not sure if this is the right forum to report this and certainly the tag #bug may not be appropriate but...
Something thatās been bothering me in the last few months of getting on HE is a couple of spelling errors that should have been trapped and corrected in the various version releases. Sorry if this is a nominal issue but I canāt help not getting stuck on it every time I am in RM
In Rule Machine 4 (and perhaps in other areas that I didnāt spend time on):
For delayed actions: Stopable ā>> Stoppable
For delayed conditions: Cancelable ā>> Cancellable - certainly both forms are valid in this case only IMO Cancellable is the more common form used (again I might be nitpicking)
If you ever start developing apps or drivers on the platform, wait until you see the DoubleTapableButton capability.
(Sorry, just a marginally related thought this brought to mind! Feel free to ignore. But while I'm on the subject, I also always have to look up the right way to spell ReleasableButton, even though that does seem to follow the dominant convention...)
I am fairly lenient on code level spelling (when it doesnāt cause syntax errors) compared to what an end-user experiences on a releasable (excuse the pun) UI
Well, in defense of @9369292f1992a7d0e654, it is such a huge undertaking: I actually have to add a single 'p' character to Rule-4.0 to fix stoppable. Split the baby, cancelable is a valid spelling so it doesn't get the extra 'l'. Besides, I already wore myself out making the change...
