Timeline for serialEvents within a class
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 11, 2016 at 0:47 | comment | added | slash-dev |
@user316182, Yes, I am sure that SerialEvent is not called from the RX char interrupt. It is called from main, which just calls loop and then serialEventRun in the never-ending for loop. You may as well just call your serialEvent code from loop. Sadly enough, there was a time when SerialEvent was dispatched from the IRQ, but it was later moved to main. See this commit. :-(
|
|
| Dec 22, 2015 at 23:00 | comment | added | CarbonMan | Yes by putting an init method in the Command class and calling it from setup() the problem was fixed. | |
| Dec 22, 2015 at 22:59 | vote | accept | CarbonMan | ||
| Dec 22, 2015 at 14:59 | history | answered | slash-dev | CC BY-SA 3.0 |