i found 2 flaws that need polish.
1. in script i was testing with, i use tab() to pre-create tab to have ability to rename it. don't know since what beta, but it started to misunderstand if icon is specified along the name.
Code: Select all
paperfolder(, , , "oe1");
$a = <selitems |>;
tab("new", "delete+|:del");
paperfolder("Sel3", $a, "|", "la");
2. actually quite strange "flaw" and i'm not even sure if it's "a bug or a feature".
if "Explicit Save Only" is ON(Autosave OFF) and non-existing paperfolder is used in script, XY creates one and saves it with items(just like if autosave would be ON). if consider it a bug, XY shouldn't create new paperfolder, and of course shouldn't save anything in it.
OR if you can make vise-versa behavior, this can become an incarnation of [named] idea.! I remember you said [named] could break old scripts = well this "flaw" can become an exception for both and no names involved.
Algorithm 1::
"Explicit Save Only" is ticked(Autosave OFF), any used paperfolders aren't saved and "temporary", BUT if non-existened paperfolder is used in script - it is created and saved(scripting way to make save even when autosave is off)[that's what happens now, as a bug]
Algorithm 2::
"Explicit Save Only" is not Ticked(Autosave ON), any used paperfolder is saved, BUT if non-existened paperfolder is used - it is not created and not saved just shown as temporary tab(an incarnation of [named] exception idea)
..or you can just fix it as described in the beginning of 2.