[Lunatixz]

I simply don't see how it could be more of an impact. There would be basically no extra time needed for "persisting" them, as they would just be being returned on the fly, just as the InfoLabels do... so why not just append them to the response "as they are set"? I realize this is all an oversimplification, and admittedly due to my own inexperience

I'm absolutely willing to give it a shot, as I mentioned in my original post... but I really have no idea where I'd even begin to look inside the codebase.

I'm simply trying to figure out a solution to this. Unfortunately, as outlined in my other thread (and demonstrated by my example), there isn't even a way to get one of the properties "on-demand", even if I know which property I'm looking at ahead of time.

Guess its one of those things will have to see when/how its implemented; however, InfoLabels are loaded into memory; nothing on the fly about it them. They are not listitems rather a dynamic representation of a single listitem key. From my recollection, there is NO connection between them and JSONRPC getDirectory.

You're saying that even though the code run in my directory, as a result of making a JSON-RPC call to Files.GetDirectory then basically ignores what metadata and properties I've attached to my ListItems, and then has to go off searching for the actual values in another, somehow persisted, location? Rather than using the ones that have just been set, by me?

You're confusing infoLabels,Listitems,JSONRPC different things. some infoLabels build from listitems and "Files.GetDirectory" does NOT return a listitem directly.

For your example; "Files.GetDirectory" would run your plugin:// path and build a listitem as per your code.