Please search the forum when you have a question on how to do something.

the concept and practice of "variables inside variables" operates fine. please post an example to the forum of what you're trying to accomplish and someone will help you figure out how to do it. this is NOT a support forum.

Already exists: F2

please take time to read the wiki: this behavior already exists as a function.

The need for this has changed somewhat over time.

I have nearly a thousand apps and use Ketarin mostly via CLI and without opening the GUI if I can help it. When I do open the GUI it would be great if those apps that have had recent errors had persistent distinctive statuses that enabled faster review.

With the other changes over the last couple years, this could now be accomplished by adding two new fields - "LastError" (a timestamp) & "LastErrorDetails" which could have the same information from the "Error" column in the popup. These could be used to persist this information and allow display with either custom columns or data export to quickly identify errors the next time I open the GUI.

{startuppath} is another option for how I use it, but since I was always using ".." to go up one directory, {startuppath} seemed redundant.

Yes, it can be considered complete now that there is working scripts to accomplish what I was after.

Either the PowerShell sample linked above or the "!" variable naming for custom columns accomplish the objectives I was after.

Checking for updates with a different drive letter always re-downloads the same files. I don't use "root", though, just ".." to get to the folder above where Ketarin is installed. I don't want downloads at the root of the drive, but stored relative to where Ketarin is located (usually store files in "K:\_Ketarin" or "?:\Support" with Ketarin installed in "K:\_Ketarin\Ketarin" or "?:\Support\Ketarin" respectively). Is using "root" necessary to avoid the re-download problem?

yes, thank you.

awesome, thanks!