espleaf/include
Fabian Schlenz 8949041812 Added effect 'rainbow'. 2021-01-19 19:52:40 +00:00
..
README Initial commit 2021-01-03 17:12:47 +01:00
config.sample.h Added a delay at bootup to allow pushing an OTA update in case of broken, looping code. 2021-01-16 18:15:17 +01:00
corner.h Removed Edge class. Wasn't needed. Nodes and Corners are anough. 2021-01-18 05:51:56 +01:00
mqtt.h We now accept and report state changes via JSON. Also added homeassistant MQTT autodiscovery. 2021-01-16 11:15:58 +00:00
my_fastled.h Added different modes. For now there are AM_CORNERS and AM_NODES. 2021-01-06 11:51:11 +01:00
node.h Added effect 'rainbow'. 2021-01-19 19:52:40 +00:00
prototypes.h Added effect 'rainbow'. 2021-01-19 19:52:40 +00:00
state.h Fixed publish_current_state() 2021-01-18 05:53:11 +01:00
syslog.h LOGln now logs to a central syslog server, if available. 2021-01-16 13:41:46 +01:00
tools.h LOGln now logs to a central syslog server, if available. 2021-01-16 13:41:46 +01:00
wifi.h Added MQTT and WiFi support. 2021-01-08 05:54:55 +01:00

README

This directory is intended for project header files.

A header file is a file containing C declarations and macro definitions
to be shared between several project source files. You request the use of a
header file in your project source file (C, C++, etc) located in `src` folder
by including it, with the C preprocessing directive `#include'.

```src/main.c

#include "header.h"

int main (void)
{
 ...
}
```

Including a header file produces the same results as copying the header file
into each source file that needs it. Such copying would be time-consuming
and error-prone. With a header file, the related declarations appear
in only one place. If they need to be changed, they can be changed in one
place, and programs that include the header file will automatically use the
new version when next recompiled. The header file eliminates the labor of
finding and changing all the copies as well as the risk that a failure to
find one copy will result in inconsistencies within a program.

In C, the usual convention is to give header files names that end with `.h'.
It is most portable to use only letters, digits, dashes, and underscores in
header file names, and at most one dot.

Read more about using header files in official GCC documentation:

* Include Syntax
* Include Operation
* Once-Only Headers
* Computed Includes

https://gcc.gnu.org/onlinedocs/cpp/Header-Files.html