dcpomatic, branch v2.15.147

Don't apply the Windows long path fix twice.

2021-05-11T14:09:20Z

Revert incorrect 'fixing' of path on Windows (#1992).

2021-05-11T12:08:42Z

This "to" path is on the ext2 drive so should not have any Windows hacks applied to it.

Open a dialogue if pinging the back-end fails on macOS.

2021-05-10T21:35:53Z

At least this means the user will get another go without losing their setup. My only theory at this point is that sometimes the backend takes a crazy amount of time to start up because of some SIP / gatekeeper type nonsense (#1990).

Fix name of macOS in the .dmg README.

2021-05-10T07:54:40Z

Attempt ping from front- to back-end several times (#1990).

2021-05-09T21:15:05Z

On macOS it seems that the backend sometimes is not started very quickly. Adding a long timeout to ping does not work, perhaps because the backend is not listening. Trying a few times seems to fix it. With this fix I saw this log: Sun May 9 23:02:51 2021: dcpomatic_disk_writer e63a485e23 started Sun May 9 23:02:51 2021: Entering main loop Sun May 9 23:02:51 2021: Writer receives command: P from the backend and Sun May 9 23:02:45 2021: Could not send ping to writer (attempt 1) Sun May 9 23:02:47 2021: Could not send ping to writer (attempt 2) Sun May 9 23:02:49 2021: Could not send ping to writer (attempt 3) from the front-end, suggesting that the first 3 pings went to /dev/null and the 4th was heard.

Fix wrapping of try-unmount dialogue on macOS (#1989).

2021-05-09T21:15:05Z

Add more logging to disk writer.

2021-05-09T21:15:05Z

Remove erroneous call to optional_node_child().

2021-05-09T20:07:51Z

Just after this we loop over all nodes, and optional_node_child will raise an exception if there is more than one.

C++11 tidying.

2021-05-09T20:07:32Z

Add some more logging to disk_writer.

2021-05-08T15:35:12Z