From 436ec7dd39d92fe775f54e857a3bd00bbf10a062 Mon Sep 17 00:00:00 2001 From: TheBestPessimist Date: Wed, 8 Mar 2023 12:45:43 +0200 Subject: [PATCH] cleanup --- .../SharedCommands/FilesFolders.cs | 16 ---------------- 1 file changed, 16 deletions(-) diff --git a/Flow.Launcher.Plugin/SharedCommands/FilesFolders.cs b/Flow.Launcher.Plugin/SharedCommands/FilesFolders.cs index 017dfa62f..6b7f0c2d3 100644 --- a/Flow.Launcher.Plugin/SharedCommands/FilesFolders.cs +++ b/Flow.Launcher.Plugin/SharedCommands/FilesFolders.cs @@ -143,13 +143,6 @@ namespace Flow.Launcher.Plugin.SharedCommands return File.Exists(filePath); } - /* - ❓ - todo does it make sense to remove Flow.Launcher.Plugin.IPublicAPI.OpenDirectory (used as Context.API.OpenDirectory(path)), - and replace with this function? - todo or the other way around: remove this function and use OpenDirectory - because i don't see the point of having 2 functions which do the same thing - */ /// /// Open a directory window (using the OS's default handler, usually explorer) /// @@ -177,15 +170,6 @@ namespace Flow.Launcher.Plugin.SharedCommands } } - /// - /// Open the folder that contains - /// - /// - public static void OpenContainingFolder(string path) - { - Process.Start(FileExplorerProgramName, $" /select,\"{path}\""); - } - /// /// This checks whether a given string is a directory path or network location string. /// It does not check if location actually exists.