Developer forums (C::B DEVELOPMENT STRICTLY!) > Development
Editor's right-click menu can open file's containing folder.
oBFusCATed:
codeman: You can use this:
--- Code: ---#if MACRO1
#elif MACRO2
#else
#endif
--- End code ---
It will make the code more readable :)
codeman:
--- Quote from: jens on July 26, 2010, 06:59:59 am ---I would prefer not to hardcode the open-commands, but making them configurable.
The configuration-defaults should be platform specific, so the user can change the default command to his/her needs.
It would be a little bit like "Terminal to launch console apps", but for all platforms and not only for non-windows platforms.
Should not be too hard to implement.
--- End quote ---
Ok what about this: In ToolsManager::LoadTools(), we currently do:
--- Code: ---void ToolsManager::LoadTools()
{
ConfigManager* cfg = Manager::Get()->GetConfigManager(_T("tools"));
wxArrayString list = cfg->EnumerateSubPaths(_("/"));
for (unsigned int i = 0; i < list.GetCount(); ++i)
{
...
--- End code ---
If the list of saved tools returns zero, then we could create a default tool to open the containing folder. For windows this would by default point to explorer, and for linux it would be xdg-open, but then you could change the tool to whatever you wanted. This tool would then be saved and loaded up as normal the next time round.
Only issue is how do we allow that tool to appear in the context menu? - that could be a new custom tool option.
What do you think?
MortenMacFly:
--- Quote from: codeman on July 27, 2010, 12:01:26 am ---What do you think?
--- End quote ---
I think what Jens means is a configuration option like in Settings -> Environment -> General settings -> "Shell to run commands in" or "Terminal to launch console programs".
If there would be another option like "explorer to launch" which can be configured (with a checkbox to "use the file name", too for Linux) and the text box is pre-configured with the platform specific default explorer (as you did now) that would be fine and most flexible.
ptDev:
I like the idea of having the option to call the system's file browser from "Tools". It makes sense to me. In fact, under Windows I added explorer to my tools, and passed arguments to make it open the directory of the active project by default.
It would be nice if a special, separated, menu option to browse the project directory would be present under "Tools" in addition to the context menu of the project manager.
codeman:
--- Quote from: ptDev on July 27, 2010, 10:08:21 am ---I like the idea of having the option to call the system's file browser from "Tools". It makes sense to me. In fact, under Windows I added explorer to my tools, and passed arguments to make it open the directory of the active project by default.
It would be nice if a special, separated, menu option to browse the project directory would be present under "Tools" in addition to the context menu of the project manager.
--- End quote ---
This is my current thinking too. The "Open containing folder" feature doesnt need its own dedicated setting field, as Morten suggested. All the functionality to do it is already available in the custom Tools menu. The correct way to do this would be to create default tools for the different platforms, and to allow cusomizing tools to be accessible from the context menu.
Maybe my code segment was not the correct way of creating pre-defined custom tools, but the idea is still sound.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version