Paweł Soja
Paweł Soja
@knro I think the issue can be closed.
I confirm. For those interested, I wrote an example showing the problem: ```cpp #include struct Foo { void operator[](size_t) { /* ... */ } operator Foo*() { return this; }...
Sure, I can also refresh this library with new features. Please just tell me is there any bug? I tried to be compatible with the old solution, hence my question....
ohh i see a bug.... I need to enable building in Actions ;)
I wanted to implement `shared blobs` in `BaseClientQt` as well, but I have doubts about compiling on windows systems. I will rewrite the implementation into a separate class used only...
BaseDevice itself includes `std::shared_ptr`, and it was once my idea not to use raw pointers (similar to `INDI::Property` / `INDI::PropertyXXX`). An example is the new method: https://github.com/indilib/indi/blob/118308fa92b3f16b013d5c1399a234ca83e0f488/libs/indibase/abstractbaseclient.h#L101 Usage: https://github.com/indilib/indi/blob/118308fa92b3f16b013d5c1399a234ca83e0f488/examples/tutorial_six/tutorial_client.h#L54 https://github.com/indilib/indi/blob/118308fa92b3f16b013d5c1399a234ca83e0f488/examples/tutorial_six/tutorial_client.cpp#L68-L74...
@knro, I think I was in a hurry. Which elements should build on Windows? Is it officially supported? When editing the code, I see inserts indicating that it is compiled...
I wrote and separated a library for network connections. I think it's worth a little work on the main `CMakeLists.txt` and separate the sources into separate libraries. This will allow...
Yes, I would like to ask for a check. I don't know as much as you, what client applications are used.
Sure, I'm starting to look for the problem.