-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
useful foldernames #64
Comments
hmm could you give a more specific example? not sure if i got what you mean. |
Well, when using the plugin paths Container.Foldername is set to "Extended info script" no matter what node you are in. What I'm suggesting is setting Container.FolderName to the title of the path that is being listed so it can be used in things like window titles / header / breadcrumb bars / whatever you want to call it, as that is more informative then the name of the script for the same reason as setting the foldername / window title to "Genres" instead of "Movies" is more informative when listing movie genres in the library. Currently I'm using a variable to achieve this:
But it could be reduced to this: $INFO[Container.FolderName] when the foldername would be set as proposed. |
tried Container.PluginCategory ? |
Yes, doesn't work |
Instead of having "extendedinfo script" in every window, it would be more useful / make more sense to set the type of info as the Container.FolderName
The text was updated successfully, but these errors were encountered: