Virtual Pins 32 - 127 / 128 - 255 and BLYNK_READ / BLYNK_WRITE

Ideas
14

Hi @Emilio,

I didn’t mean to imply that Blynk.h doesn’t compile or not work. It works fine. I just don’t think the developers would’ve put the “instead of” warning,

#warning "Please include a board-specific header file, instead of Blynk.h (see examples)"

in it had they intended us to use it.

I wish the developers would just gut Blynk.h. If my understanding is correct, Blynk.h is needed in order to directly #include files such as Blynk\BlynkDetectDevice.h. It serves to identify the Blynk library.

Better yet, I wish the developers would restructure the nested #includes and preprocessor directives such that we could more easily,

#undef BLYNK_USE_128_VPINS

from a sketch without having to jump through so many hoops.

On a related note … you’ll notice, with #undef BLYNK_USE_128_VPINS,

  #define V32 32
  #define V33 33
  ...
  #define V127 127

are no longer defined. Of course,

  #define V128 128
  #define V129 129
  ...
  #define V255 255

were never defined. I just use integers (0, 1, … 255) to reference the virtual pin numbers,

/*
 * Controller Widget Virtual Pins
 */
#define BUTTON          0
#define SLIDER         32
#define TEXT_INPUT    128
#define NUMERIC_INPUT 254

Thank you for taking the time to test this.

Joe

1 Like