This looks very nifty! What I find inconvenient, however, is that th

Interface consistency with SerialDebug about remotedebug HOT 2 CLOSED

joaolopesf commented on May 14, 2024

Interface consistency with SerialDebug

from remotedebug.

Comments (2)

JoaoLopesF commented on May 14, 2024

HI, I agree that, and I will work in one solution

from remotedebug.

JoaoLopesF commented on May 14, 2024

Hi, I just upload a new version: 1.5.8 New macros to compatibility with SerialDebug (can use RemoteDebug or SerialDebug)
As SerialDebug is based in macros and RemoteDebug is based in C++ class, due this functionality,
not is possible 100% compatibility, I sugest that use #defines to use one or another library, example:

#define USE_REMOTEDEBUG true

and:

#ifdef USE_REMOTEDEBUG
// RemoteDebug

RemoteDebug Debug;
#endif

#ifdef USE_REMOTEDEBUG

// Initialize RemoteDebug

initializeRemoteDebug();

#else

// SerialDebug

#ifndef DEBUG_DISABLE_DEBUGGER

// Add Functions and global variables to SerialDebug

// Add functions that can called from SerialDebug

//debugAddFunctionVoid(F("function"), &function); // Example for function without args
//debugAddFunctionStr(F("function"), &function); // Example for function with one String arg
//debugAddFunctionInt(F("function"), &function); // Example for function with one int arg

// Add global variables that can showed/changed from SerialDebug
// Note: Only global, if pass local for SerialDebug, can be dangerous

debugAddGlobalUInt16_t("motorSpeed[0]", &mMotorControl.mMotorSpeed[0]);
debugAddGlobalBoolean("motorForward[0]", &mMotorControl.mMotorForward[0]);
debugAddGlobalUInt16_t("motorSpeed[1]", &mMotorControl.mMotorSpeed[1]);
debugAddGlobalBoolean("motorForward[1]", &mMotorControl.mMotorForward[1]);

#endif // DEBUG_DISABLE_DEBUGGER
#endif //USE_REMOTEDEBUG

from remotedebug.

Recommend Projects