Implemented steps reset function for bma421

[BNolet]

• added (useless) param to make compatible with bma42x.c
• implemented reset_step_counter in bma421.c/h

[BNolet]

Just a little backstory regarding this commit.

I originally figured it would be as simple as using the existing reset function from steps.py pedometer app in wasp-os but that ended up taking quite a long time (on the magnitude of several seconds) every time I tapped the app to reset the pedometer to 0. So I dug and then I found the reset function was actually meant to be more efficient.

Once I found the source of the issue, it was simply a matter of implementing the proper reset function. The issue is 1. I know very little C, and 2. The setter function in bma42x.c was not immediately compatible with the reset function of bma421.c. So I had to add some useless param to the library.

I'm sure there's a less hacky way to do this but I'm sure that can be figured out by someone with more C competence than I.

[daniel-thompson]

I'm afraid you are right that adding a useless argument simply to allow you to treat bma421_reset_step_counter() like a setter method is hacky.

bma421_reset_step_counter() is not a setter function so you should not wrap it like a setter. It is an action (like init or write_config_file) and should be wrapped in the same way as init.

See bma42x_BMA42X_init and BMA4_EXPORT_OBJ(init) for examples of the correct code to copy and note that the wrapping code must use the same name as the underlying C API (e.g. the function that should end up in the locals dict table should be BMA4_EXPORT_OBJ(reset_step_counter) ).

[BNolet]

Thank you Daniel for the guidance on this one as well as the proper explanation. I really appreciate being able to contribute to the project :)

I've made the requested change after testing that the result is the same with my PineTime