Unlock system when copying an image

The locking does not depend on the process. When the Systemback is running, the lock is active.

This is not efficient.
Greetings.

Maybe, but this is the current situation. If I am going to design the next version, I will considering your opinion.

I read on the net that they are preparing a new project similar to yours.

This is a great news.
Currently I just started the thinking about the next version, and writing the basic things (I want to simplify the Systemback engine). But if there a new developer group with a similar application, maybe my work is ended.
What is this new project?

I think I understand why the project does more.
It would be desirable for you to decide what to do. I do not understand why you keep up to date a project that is obvious, you are interested in little and cares even less.
Having a new version in very long times is useless. I'm sorry about your attitude often incomprehensible. Unfortunately, you know that you are insensible at the point and keep on loitering on a wait state. What are you waiting for to continue or close? I use an automatic translator and I do not know if I have fully made sense.

I have suspended the Systemback development because of my personal things. But I did not rule out the possibility of continuation. So the project progress is stopped. If I can I help in the questions and others, but I will not touch the current code.