Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

Tidy main context menu

<< < (2/6) > >>

Alpha:

--- Quote from: oBFusCATed on September 01, 2012, 05:14:25 pm ---"Why have you removed XXX, I use it and like it and I want it back, else I switch IDEs?".

--- End quote ---
I am not planning to remove any functionality, just reorganize to make the most used items easily accessible, and hopefully decrease the size of the menu.


--- Quote from: oBFusCATed on September 01, 2012, 05:14:25 pm ---So, I think the best option is to provide an UI for hiding certain item. By name or by regexpr.

--- End quote ---
This is also something I will be trying to do.

dmoore:
A long time ago, mandrav, the founder of the project had started work on a registry for toolbar/menu/popup menu items. This would make it much easier to offer a UI that would give the user more control over what shows up and in what order. Apparently he lost the work, but the idea is a good one. A lot of the clutter that plugins create could then be turned off by default.

Alpha:
That sounds like an interesting idea, but I am not certain I understand exactly what you are describing.  Do you have more details?

Alpha:
Are there any objections to hiding CC's "Find ... of: ..." entries when (1) the current file is not C/C++, and (2) the item is in a string/comment?

MortenMacFly:
First of all, these items I use regularly:
- Find declaration/implementation/(...) - all of them
- Insert class methods with...
- Swap header/source
- Folding: fold/unfold all
- all of aligner
- Permanently highlight...
- Add ToDo item...
- Show file in project tree
- Spelling suggestions -> should be way more at the top, btw!

The Find... options could be grouped which would shrink the menu a lot. But I honestly think the best way would indeed be a registry. The menu items used here are really user specific, so everything you think is good, won't be for others (remember the simple switch header/source discussion). In the end the core knows all it needs to know for a registry, as plugins have register their menus.


--- Quote from: Alpha on September 02, 2012, 04:37:54 am ---Are there any objections to hiding CC's "Find ... of: ..." entries when (1) the current file is not C/C++, and (2) the item is in a string/comment?

--- End quote ---
This is such a case: Think about that you don't know exactly, what items are C/C++ - its a user option.

Navigation

[0] Message Index

[#] Next page

[*] Previous page