fix for 2.2

[flightlex]

No description provided.

[Folleach]

Thank you for PR!
I'll watch it soon.

So far, I can say that two merge commits in your repository were unnecessary. They refer to the PR numbers that are made in your repository and do not make sense.
You could make separate branches for your functionality, then do PR with them in the origin repository.
Once the PR is in the main branch, you can simply pull your main branch from the origin repository.

Now, since your commit is not signed, I can make a cherry pick during the merge. Can I?

[flightlex]

Thank you for PR! I'll watch it soon.

So far, I can say that two merge commits in your repository were unnecessary. They refer to the PR numbers that are made in your repository and do not make sense. You could make separate branches for your functionality, then do PR with them in the origin repository. Once the PR is in the main branch, you can simply pull your main branch from the origin repository.

Now, since your commit is not signed, I can make a cherry pick during the merge. Can I?

go ahead

[Folleach]

I've cherry pick this commit to 1f4e91e
Then I made some fixes, described them in the commit 24582c6

Released in v0.2.28

GitHub doesn't match changes from origin to the pull request, so I'm closing this PR