ESP_IOT v2.5
IOT ESP Coding
ChainButtonStruct Struct Reference

#include <PreferencesController.h>

Collaboration diagram for ChainButtonStruct:
Collaboration graph

Public Attributes

char * chainUse
 chain use string for debugging printout More...
 
char * classType
 
int buttonNumber
 
char * setString
 the set strings, val strings, device strings More...
 
char * valString
 val strings More...
 
char * deviceString
 
int pressKind
 press kind: 0 = short press, 1 = long press, 2 = long long press, -1 any, 100,101,102,103 Yoystick left, top, right, bottom More...
 
char * SMARTAddress
 
boolean isDOCFOLLOW
 
boolean buttonFinalized
 if finalized yet ... if the set/val are defined.. More...
 

Detailed Description

1.22.26 wrap the button define ChainbuttonStruct

Definition at line 365 of file PreferencesController.h.

Member Data Documentation

◆ buttonFinalized

boolean ChainButtonStruct::buttonFinalized

if finalized yet ... if the set/val are defined..

Definition at line 398 of file PreferencesController.h.

◆ buttonNumber

int ChainButtonStruct::buttonNumber

each in chainUseCount references the 4 arrays index the buton numbers

Definition at line 373 of file PreferencesController.h.

◆ chainUse

char* ChainButtonStruct::chainUse

chain use string for debugging printout

Definition at line 367 of file PreferencesController.h.

◆ classType

char* ChainButtonStruct::classType

string describing the module, etc THis can be short "BC", or long .. but trying to shorten for EPROM storage

Definition at line 370 of file PreferencesController.h.

◆ deviceString

char* ChainButtonStruct::deviceString

the device strings Note, if "localhost" then this is an INTERNAL message (like feed) so use bluetooth or whatever network works

Definition at line 381 of file PreferencesController.h.

◆ isDOCFOLLOW

boolean ChainButtonStruct::isDOCFOLLOW

2.1.26 Nice day add isDOCFOLLOW (where a $DC or $DOCFOLLOW is defined Here .. is a DOCFOLLOW message arrives .. it searches for the DOCFOLLOW (if more than one) and replaces with SMARTAddress with the address specified .. then sends getSmartDefn and waits for reply BUT . the next DOCFOLLOW that shows up, it will override the SMARTAddress and start again. The BUTTON will perform the operations specified as if a SMARTAddress (and a MQTT definition)

Definition at line 395 of file PreferencesController.h.

◆ pressKind

int ChainButtonStruct::pressKind

press kind: 0 = short press, 1 = long press, 2 = long long press, -1 any, 100,101,102,103 Yoystick left, top, right, bottom

Definition at line 383 of file PreferencesController.h.

◆ setString

char* ChainButtonStruct::setString

the set strings, val strings, device strings

Definition at line 375 of file PreferencesController.h.

◆ SMARTAddress

char* ChainButtonStruct::SMARTAddress

2.9.26 Superbowl Win, L Vonn crash ouch add the SMART Address here in case of the new indirection. Thus if a message shows up, the message info might change <class, buttonNum, pressKind, $SMART, uuid.flownum, DEV> SMARTAddress = uuid.flownum

Definition at line 388 of file PreferencesController.h.

◆ valString

char* ChainButtonStruct::valString

val strings

Definition at line 377 of file PreferencesController.h.


The documentation for this struct was generated from the following file: