![]() ![]() Valid values are: Name, Size, Type, Date. Type of information to sort the entries by. Semi-colon separated list of file extensions that limits the type of files to be included.Įxample: If Extensions="jpg png", only. If set to 1, file extensions are removed when used with Type=FileName. If set to 1, protected operating system files are included. If set to 0, hidden files and folders are ignored. folder (representing the previous folder) will be included. The number of items to be indexed at one time. Plugin commands FollowPath and PreviousFolder are disabled, and ShowFile, ShowFolder, and ShowDotDot options have no effect. If set to 2, the plugin indexes all files in the folder tree defined in Path. This option does not index specific files in sub-folders. If set to 1, the plugin searches all sub-folders updating only the file count, folder count and overall folder size. This can be used to ensure that a large folder structure is fully read before other actions are taken. Parent measure options FinishActionĪction to execute when the plugin has completed reading the folders and files. In a child measure, defines the parent measure to read values from. Note: While #Variables# can be used in the parent Path option, cannot, as this is ambiguous with the parent definition in a child measure. By default, the This PC (formerly My Computer) folder is used. In a parent measure, defines the path of the folder to read. OnUpdateAction=!CommandMeasure MeasureFolder UpdateĪll general measure options are valid. Be aware that having the plugin physically access the disk has a performance cost, and care should be taken to use an appropriate UpdateDivider. If it is desired that a folder be monitored for new or changed files, the Update plugin command should be used in conjunction with an OnUpdateAction statement to keep the measure current with changing disk information. If the options on the parent measure are changed dynamically with !SetVariable or !SetOption, the Update plugin command will need to be used to update the values. Important Note: A FileView measure will not re-read the disk information on a normal update cycle or using UpdateDivider on the measure, nor when the !Update / !UpdateMeasure bangs are used. This will allow a skin to "scroll" through the files and / or folders in a dynamic way. However, the information for all files and / or folders are obtained by the plugin, and subsequent or previous entries can be assigned to the three indexes by using !CommandMeasure statements described below. In these examples, three indexes are created due to the Count=3 option on the parent measure. The values of the three child measures are now the FileName, FileSize and FileDate information from the first file (Index 1) of the parent measure. These can then be used with MeasureName and other options in meters.Īnother way to use the information in child measures is: The values of the three child measures are now the FileName information parsed into Indexes 1 through 3 by the parent measure. The information is used in subsequent "child" FileView measures: In this example, this "parent" measure will obtain name, size, date and icon information about all files in the selected folder, then create three Index values for the first three files. A main "parent" FileView measure is used to obtain all the information for a selected folder, and then "child" measures are used to read individual entries from the parent using the Path= option.įileView measures take the form: It can also search recursively through all the subfolders of the selected folder to obtain the totals for count and size.įileView operates with a "parent / child" approach. It counts the number of files and folders and obtains the combined size. The plugin gathers all the folder and file names, sizes, dates and icons in the selected folder. Information=Shows the RAM usage in percent, with a glowing ring background.Plugin=FileView retrieves information about folders and files. Text=Item: #CRLF#Field: #CRLF#Value: #CRLF#Raw: #CRLF#CRLF#Item: #CRLF#Field: #CRLF#Value: #CRLF#Raw: If this is so, then setting the Show CPU/GPU temperatures to ON in the suite's Settings skin should solve the "issue" (though you said the CPU temp works, so I might be wrong, after all): I suspect that the issue is that the GPU temp is by default hidden in the said skin, due to the #TempsToggle# variable value at the end of the code. ![]() License=Creative Commons Attribution-Share Alike 1) Information=Shows the GPU usage in percent, with a glowing ring background. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |