app_button_init

[JohnBrown]

It seems that in SDK9 the APP_BUTTON_INIT() macro has disappeared, and with it the extra argument that determines whether the scheduler is used or not. However, the documentation still clearly refers to both the macro and the USE_SCHEDULER argument. Can anyone help me to understand this?

[Susheel Nuguru]

That is because the example\bsp\bsp.c file has changed in SDK 8.0 to not using that MACRO and all the examples uses bsp.c file.

Also if you want to postpone your button handler execution using the scheduler, you can do that even from the handler called by app_button library. Scheduler is seperate module you can use as per your application requirements, that is probably what the SDK team tried to do. Remove the dependency.

[JohnBrown]

Actually I did want to use the scheduler. My app was started using the ble_lbs example, that seems to have disappeared also from SDK9. No matter, I will attempt to write the button handling for my application from scratch.

[Susheel Nuguru]

You seems to have a lot of patience. Why not just copy the app_button.c and app_button.h and bsp.c and bsp.h files from the SDK which were working for you before and put it in SDK 9.0 would save you a lot of time. If you encounter any problem, i will try to help you.

[JohnBrown]

I don't believe there was a bsp.c in SDK6. But anyway, I handled a 4 by 4 keypad matrix with my own code, it shouldn't take long to modify it for a a simple 5 way keypad.

[JohnBrown]

But the longer answer to you question is that, not working for Nordic, I have no idea what other demons might be unleashed if I start copying code from one SDK to another. While I am full of praise for the support given here, there is now so much documentation that it's hard for mere mortals like me to keep a grip on it all.

[Susheel Nuguru]

I understand, well all i can say is try what suits you best, and we will try to help you when needed.