You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I try to perform a search, in the respective field, the application links, located in the system paths, ("ProgramData\...\StartMenu" and "user\AppData\...\StartMenu", see Fig. 2), are found (recursively) as expected.
However, links that are in the folders (and subfolders) of the custom directory (Figs. 1 and 3) are not found, unless they are in the root folder (that is, the search is not recursive).
Bug (?!) or any/some configuration problem (?!)... or is it an intrinsic limitation of STM behavior?
OS: Windows11 23H2
Version 1.3.5.0 (UWP)
The text was updated successfully, but these errors were encountered:
I tried to make several configuration changes (the rational ones) and tried the portable version of STM (my current version is UWP), thinking that there might be some limitation and/or bug in the latter, but the result was always consistent: the recursive folder search created in the root directory cannot be performed unless the path is included in Settings > Directories (Fig. 2)!
But, in this last situation, to have a searchable Custom Folders Menu, we would have to do without placing system folders (Fig. 2) to avoid a mess in the Menu!
In other words, it is an intrinsic limitation of the App itself... which I lovef, but which has this drawback!
Will it be possible to implement this functionality in STM?
This is the challenge that I, respectfully, leave to our Developer!
When I try to perform a search, in the respective field, the application links, located in the system paths, ("ProgramData\...\StartMenu" and "user\AppData\...\StartMenu", see Fig. 2), are found (recursively) as expected.
However, links that are in the folders (and subfolders) of the custom directory (Figs. 1 and 3) are not found, unless they are in the root folder (that is, the search is not recursive).
Bug (?!) or any/some configuration problem (?!)... or is it an intrinsic limitation of STM behavior?
The text was updated successfully, but these errors were encountered: