reachim wrote:I think it would be better to make a variable in the RemoteXY structure that will hold the time in UNIX format. Then everyone can use it as they wish.
Nearly a whole year later, and nothing on this on the horizon.
Totally agree with your suggestion of making the OS time/date available to the controller, it would certainly simplify a lot of tasks.
Similar to the "Sound" widget, the variable(s) would only appear in the interface if a "TimeDate" object is included in the GUI.
The idea of using UNIX format is good, as it would allow for precise "elapsed" times, extended across minutes, hours days etc. boundaries, rather than having yy, mm, dd, hr, mn, sc variables, which would be harder to deal with. But what about the option to have either... you can then use as appropriate to your project.
I have made many suggestions for ideas and improvements, many of which have not even been answered by the developer.
"Button Groups" - the concept of using a uint8_t for a single boolean "state" is grossly overkill, the same applies to LEDs (or just "indications"). Enhancements to "Sound" objects that would enable us to more easily interact with them.
I totally like RemoteXY, it has an air of "simplicity" that makes it great for the hobbyist, but it also has the potential to be so much more than it is, and I would be happy to pay more for extended licensing to unlock "advanced" features etc.
We need to keep up the pressure to move this app forwards ....
2B, or not 2B, that is the pencil ...
