Theo Sanderson

Hi, that is at present correct. I agree that this would be a useful feature. As you probably saw, you can supply the _contents_ of the file in the URL:...

Worked in this commit https://github.com/theosanderson/taxonium/commit/4c03b0cfd70b453403592913a705f1798dff8af9 . May be related to treenome.

(@amkram for info I thiink this got broken by the Treenome merge -- which if so is my bad, I should have checked! -- it used to work like this...

I can't reproduce this atm. If I close the backend window all windows close (intended behaviour). If I close the Electron-based front-end I am able to reopen it with the...

This definitely isn't expected behaviour. I can't (immediately) reproduce it in the sense that if I just load a tree and do some basic stuff then CPU usage drops to...

Oh weird - thanks. In my check I had loaded in the browser, which does not (in my experience) do this. But I can see something similar when I use...

Suggested workaround (not expressed clearly) was to open the `https://taxonium.org/?backend=http://localhost:xxxx` URL in the browser. That shouldn't be any slower as it's doing the same thing. However I'm no longer convinced...

For writing _backend_ logs to a file you should be able to use: `/Applications/Taxonium.app/Contents/MacOS/Taxonium &> ~/log.txt`

Looked into this a bit. - As above, backend seems fine mostly, this issue is about front-end issue - No React re-rendering is going on when Idle in the frontend...

Reopening this in case we think of anything else..