What I mean is that I currently have to use Type=FileName for getting the file name without path.
The path is specified in the parent: Path="#mCategoryPath#\#mMediaListPath#" but as I use Recursive=2, the path is dynamic within that parent. But you cannot obtain the path dynamically via the parent unless changing the actual variables. This path remains static.
This static path is the problem. Although you are obtaining the files recursively, the path to those files is not obtained. To display those files within file view, Rainmeter MUST be getting that info itself without further measures. So I am trying to state that it would/should be much easier if there were a variable that can respond to this recursive function, obtaining the path depending on which file you click to show, thereby updating the path depending on where the file is.
Like this:
Parent path=D:\Folder
With Recursive=2 it finds the following: D:\Folder\Pics1 and D:\Folder\Pics2, as well as items within it's root.
So now we have:
D:\Folder - containing a few jpg's
D:\Folder\Pics1 - containing a few jpg's
D:\Folder\Pics2 - containing a few png's
All of which will be ordered by name within a single file view set up.
Let's say for example that they contain items from the folders like this:
Index1 - D:\Folder
Index2 - D:\Folder\Pics1
Index3 - D:\Folder\Pics2
Index4 - D:\Folder
Index5 - D:\Folder\Pics2
Index6 - D:\Folder\Pics2
Index7 - D:\Folder\Pics1
Index8 - D:\Folder\Pics1
In order to display this list, Rainmeter must know the location of a file, as you stated, it has to obtain this info from a measure by it's nature. As it stands, this is exactly what it must be doing in order to display each of these items, yes?
So, why not have a built in variable that works in much the same way as #CURRENTFILE# does. But instead of getting info for the current skin file, it obtains the path of that index item in full.
Idk, maybe I'm talking sh*t!!!![:lol:]( "LOL")
The path is specified in the parent: Path="#mCategoryPath#\#mMediaListPath#" but as I use Recursive=2, the path is dynamic within that parent. But you cannot obtain the path dynamically via the parent unless changing the actual variables. This path remains static.
This static path is the problem. Although you are obtaining the files recursively, the path to those files is not obtained. To display those files within file view, Rainmeter MUST be getting that info itself without further measures. So I am trying to state that it would/should be much easier if there were a variable that can respond to this recursive function, obtaining the path depending on which file you click to show, thereby updating the path depending on where the file is.
Like this:
Parent path=D:\Folder
With Recursive=2 it finds the following: D:\Folder\Pics1 and D:\Folder\Pics2, as well as items within it's root.
So now we have:
D:\Folder - containing a few jpg's
D:\Folder\Pics1 - containing a few jpg's
D:\Folder\Pics2 - containing a few png's
All of which will be ordered by name within a single file view set up.
Let's say for example that they contain items from the folders like this:
Index1 - D:\Folder
Index2 - D:\Folder\Pics1
Index3 - D:\Folder\Pics2
Index4 - D:\Folder
Index5 - D:\Folder\Pics2
Index6 - D:\Folder\Pics2
Index7 - D:\Folder\Pics1
Index8 - D:\Folder\Pics1
In order to display this list, Rainmeter must know the location of a file, as you stated, it has to obtain this info from a measure by it's nature. As it stands, this is exactly what it must be doing in order to display each of these items, yes?
So, why not have a built in variable that works in much the same way as #CURRENTFILE# does. But instead of getting info for the current skin file, it obtains the path of that index item in full.
Idk, maybe I'm talking sh*t!!!
Statistics: Posted by sl23 — Today, 5:24 pm