Tilen Majerle
Tilen Majerle
> As far as I know in C there is no guarantee that an `unsigned long` can be converted to `void *` and vice versa. There are platforms out there...
Then the best proposal is to start the thread passing the data index and retrieving the data by: ```c void* get_thread_data(ULONG index) { return data_pointers[index]; } void thread_func(ULONG value) {...
IMHO It should be void* and nothing else. Everything else is a workaround of a bad design.
> I would recommend adding a new `tx_thread_create2()` that supports `void *`, leaving the old `tx_thread_create()` intact. Or a threadx options where user can define the parameter type.
> A pointer points to an address of memory. The address of the memory is also a ULONG-compatible type. Not the case.
Fully support this. It should have been done from the day 1.
An update. The lights control via labels does not work properly. Steps to reproduce: - Create a new label - Set the light entity to that label, it can be...
I've run more cases. Now I can observe that if I put my light entities into a home assistant group, and call `light.turn_on` on this new group light entity, adaptive...
I've played with the tolerance setting, and it seems that tolerance is the cause of troubles. When I disable the tolerance on all entries, the BT climate entity aligns with...