Christoph Bartelmus

Please don't remove the typedef. It reminds you that a variable contains timing information and you need to use the given macros to extract the microseconds value. Using int or int32_t won't make much difference in real-world scenarios. There's no danger that this code is used on 16-bit platforms.

The specific reason is that it is not required. The usecase can perfectly be implemented using ptrail and foot (foot is sent as "space pulse"). pre and post are separators between two compontents. If one component does not exist, there is no need for a separator. Please add a warning as suggested by Bengt. Cheers, Christoph

"pre/post" was originally meant to be a separator between "data" and "pre_data/post_data". If pre_data/post_data is empty of course no separator would be required. Please update the documentation accordingly. What initially was intended by the OP could probably be implemented using the "foot" field.

Pre was originally meant to be a separator between data and post_data. If post_data is empty of course no separator would be required. Please update the documentation accordingly. What initially was intended by the OP could probably be implemented using the "foot" field.

Remote config parsed twice at lircd start-up

Yes, it does. lircd needs to get timing data for an initial transmission and a repeated...

Remote config parsed twice at lircd start-up

Don't get what you mean by "parse each remote button in the config twice". Your log...