You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently content files are named like that: <n>.txt and <n>.bin. It was decided that it's not a good naming scheme.
If a revision uses the same binary data as a previous one, it is marked in struct Revision, but not in meta.json. It introduces this bug: if you change a hypha with binary data, the old picture is shown only until you reload the program.
What to do
Save files with numbers in their stem, but with extension matching their mime-type.
If it is hard to decide what extension to use, fall back to .txt and .bin.
Save filenames to meta.json
The text was updated successfully, but these errors were encountered:
Currently content files are named like that:
<n>.txt
and<n>.bin
. It was decided that it's not a good naming scheme.If a revision uses the same binary data as a previous one, it is marked in
struct Revision
, but not inmeta.json
. It introduces this bug: if you change a hypha with binary data, the old picture is shown only until you reload the program.What to do
.txt
and.bin
.meta.json
The text was updated successfully, but these errors were encountered: