Re point 1:
I was referring to the recycle bin - that is, deleted files, and not to the management of files in use. You can’t seem to empty the recycle bin.
Re point 2:
I think this is a misunderstanding (may be due to my Enlish). There are two different topics being discussed in this thread. At the beginning it was about the fact that SeaTable, in my opinion, has problems with inserting screenshots and with files that come from screenshots. This problem exists in ALL bases. Her last statement on this was: “I’ll test that”. I have hope that this problem can be solved.
Later, the problem with the error message when simply inserting screenshots was added. This problem existed only in ONE base. After restoring a backup, I solved the problem for myself. I have no hope that we will ever find out what broke this base.
I have visualized the process of pasting from the clipboard for better understanding. To do this, I created a new test base, and created an image column there. The row height is set to “fourfold”. Then I took a screenshot of a square Python icon (clipboard). It doesn’t matter with which app the screenshot is made.
If you want, I can also send you this base (dtable). Maybe there are other users here who can confirm the problem …
Thanks rdb for taking the trouble to follow it up!
It’s a great mystery. The good thing about SaaS is that you can blame everything on the SaaS operator. But who should I blame it on now?!
I like the new possibility of displaying formatted text at four times the line height. But until further notice, I can unfortunately only use the single line height under these circumstances.
I have now tried it on a completely different computer. The same result. So I can rule out the possibility that it is due to a special system configuration.
Surprisingly, it works quite well when I select “File” as the column type. Then I can’t paste a screenshot from the clipboard directly. But a screenshot that I save as a file works (in contrast to the type “Picture”).
Of course, this would be a very cumbersome workaround. But it shows that something is wrong here!
I am sorry that I cannot solve your problem. I cannot reproduce your problem and you are the only one to report this issue.
If I understand you correctly, you found some workarounds (i.e., saving the file first or using the column type “file”). Please understand that I will not pursue this topic any further and save the resources.
