Hi!
The Directory history menu (slow right click on current directory line or click on small down pointing triangle) should have a "Clear history" option (as bottom item maybe).
Directory history
Moderators: white, Hacker, petermad, Stefan2
-
Balderstrom
- Power Member
- Posts: 2148
- Joined: 2005-10-11, 10:10 UTC
Still, it would be a convenience to be able to click "clear history" on an ad hoc basis without having to program/implement something ourselves. Not all users will have the skill.
There is a difference between routine behavior and instantiated behavior.
IMO TC should distinguish between the two ("Save on exit" via the INI vs. "clear history now" via a top-level UI control), especially considering how easy it would be to code such a feature into the history menu, and how useful it would be to many of us.
There is a difference between routine behavior and instantiated behavior.
IMO TC should distinguish between the two ("Save on exit" via the INI vs. "clear history now" via a top-level UI control), especially considering how easy it would be to code such a feature into the history menu, and how useful it would be to many of us.
Licensed, Mouse-Centric, moving (slowly) toward Touch-centric
-
Balderstrom
- Power Member
- Posts: 2148
- Joined: 2005-10-11, 10:10 UTC
@ JohnFredC
I agree, completely. The wincmd.ini should be just that: a configuration file.
All Histories, by default, should be separate files (or optionally registry contained) and clearable while running. The option to redirect sections of the ini is a bad hack imho -- which unfortunately works, which means no other implementation will be done.
Similiar to the plugin system: many of the plugins provide functionality that many would agree should be core functionality. But once a plugin shows up to provide a feature it becomes that much less likely that TC will implement that feature. Some plugins break between TC releases, sometimes they get abandoned completely, their source is rarely provided and in many cases their are far too many plugins to choose from - which all do the same basic task.
An example of this: ButtonBar drop down menus. TCMenu provided this functionality many years ago. The internal implementation took a very long time to show up, and again IMHO the internal solution isn't as good. TCMenu allows you to have alternate IconSizes, Colorize/Skin the menu background and define a default action for the menu. I continue to use TCMenu instead. The internal solution should have been better, not less featureful.
I.E. Allow multiple default actions, Which could be implemented in any number of different ways.
I agree, completely. The wincmd.ini should be just that: a configuration file.
All Histories, by default, should be separate files (or optionally registry contained) and clearable while running. The option to redirect sections of the ini is a bad hack imho -- which unfortunately works, which means no other implementation will be done.
Similiar to the plugin system: many of the plugins provide functionality that many would agree should be core functionality. But once a plugin shows up to provide a feature it becomes that much less likely that TC will implement that feature. Some plugins break between TC releases, sometimes they get abandoned completely, their source is rarely provided and in many cases their are far too many plugins to choose from - which all do the same basic task.
An example of this: ButtonBar drop down menus. TCMenu provided this functionality many years ago. The internal implementation took a very long time to show up, and again IMHO the internal solution isn't as good. TCMenu allows you to have alternate IconSizes, Colorize/Skin the menu background and define a default action for the menu. I continue to use TCMenu instead. The internal solution should have been better, not less featureful.
I.E. Allow multiple default actions, Which could be implemented in any number of different ways.
Last edited by Balderstrom on 2009-08-26, 14:36 UTC, edited 1 time in total.