Timofey Kazantsev

BTW, the last example is indirect confirmation that fix of #80 is not breaking things, and call to the `ValidatePtr` is unnecessary. C-side of API still will fall back to...

I still think it is good idea, as I started to add more fields to my custom project class for keeping it serializable. For example, now it is `self._filename`.

pity, but just now I can't see the reason.. More than, I used this function a lot last year... Need to test. I'll try to check at evening

I found it very strange and, probably, not related to the package... If I have time Sunday, maybe I'll try to reproduce the bug. But... probably, something is wrong with...

See [`reapy.connect`](https://github.com/Levitanus/reapy-boost/blob/master/reapy_boost/tools/network/machines.py#L89) function. Also, I've already got a request to modify this part of code, so, in [`reapy-boost`](https://github.com/Levitanus/reapy-boost) it's possible to definitely specify host and port.

P.S. Commenting lines 114-115 of `plugin.py` solves the problem

In `reapy-boost` markers have no bugs and better functional https://github.com/Levitanus/reapy-boost/blob/master/reapy_boost/core/project/marker.py#L123

[jms5194](https://github.com/jms5194), I haven't also updated my fork for a couple of years, as moved to rust reaper extensions, but at least I'll manage all pull-requests, that come to the fork....

Can you describe all steps that leaded to resolving the issue? It looks similar to #135, or #130, and, since I hadn't time for debugging of the cases I can't...