The unified command system will probably never be implemented as it's described in the wiki. The reason is that it includes some changes that would break compatibility with older version.
It's a real pity At least, I hope Ghisler implements some changes to command system or introduce macros, so users can make things like, for instance, "Copy and add to queue" in only one keystroke. Instead of F5 + F2, somebody can select for instance F11. I guess, people is desperating waiting for this...
2ArielP
Macros have never been part of the unified command system. It basically denounces that there are several types of commands that work and behave different. That's why my suggestion called unified command system.
I'm not against macros but this is another story.
Last edited by Lefteous on 2006-06-08, 05:58 UTC, edited 1 time in total.
05.06.06 Release Total Commander 6.55 beta 2
01.06.06 Fixed: Crash in internal desktop search when entering a search string longer than 255 characters.
01.06.06 Fixed: Long delay when the unified command systems update menu captions.
01.06.06 Fixed: Endless loop when trying to execute a user macro which doesn't end with a line break.
31.05.06 [b]Fixed: Unicode version only:[/b] Fixed a bug where paths could be longer than 259 characters although not supported by most shell functions.
As you can see it's just a bugfix release. Nothing really worldshaking.
Should I change my sig
I think not, but it would be nice...
Very nice, but heck, still waiting
Ambiguity succeeds where honesty dares not venture.
Macros have never been part of the unified command system. It basically denounces that there are several types of commands that work and behave different
2Lefteous
I have read in the past the proposition of UCS and I know it is something more complete than macros, but I was talking about macros as a workaround to the fact that UCS won't ever be implemented. I think macros is easier to implement for Ghisler, and a first step could be add macros that involve internal commands, like the one I mentioned before. Just to dream:
It's so funny that people ask for for an early version of a history list for a version which is announced as bugfix version.
Nothing funny. Your know that Ghisler might have overlooked some bugreport from the fora (at least I know a bugreport made in few weeks age which is still unanswered). So if I had the list of fixes I would see whether he's awared of the bug or not. And point it to him again.
That was the reason of my request.
F6, Enter, Tab, F6, Enter, Tab, F6, Enter, Tab... - I like to move IT, move IT!..
Lefteous wrote:Okay here are some words on this. The unified command system will probably never be implemented as it's described in the wiki. The reason is that it includes some changes that would break compatibility with older versions.
What compatibility will be broken?
TC doesn't create its own document filetype (like .doc, .psd etc) so the next version will not be able to open it.
INI files are the only tc generated files AFAIK, and i don't see why new format of ini files couldn't be introduced if it is necessary for UCS.
Well of course there is a way not to break compatibility: Introduce for example the suggested new structure files but still support the old menu and button bar files (and others). The downside is of course that supporting the old format means overhead and maybe even more confusion for the user than the existing system.
Last edited by Lefteous on 2006-06-08, 10:01 UTC, edited 1 time in total.
Lefteous wrote:The downside is of course that supporting the old format means overhead and maybe even more confusion for the user than the existing system.
Doesn't need to be supported old and new systems. Old files can be imported and saved with new systems parameters, keeping the structure as intact as possible.
Doesn't need to be supported old and new systems. Old files can be imported and saved with new systems parameters, keeping the structure as intact as possible.
Well of course there is a way not to break compatibility: Introduce for example the suggested new structure files but still support the old menu and button bar files (and others)
But sometimes you have to break compatibility. When you make big and important changes you have to cross the borders.
Well you should have learned from several author statements that compatibility is mandatory from his point of view.
This does not only apply to command related things. There is for example the calling of custom column configurations by ids. This is competely unusable (Move or delete a config...) . A redesign would mean custom column definitions wouldn't work in a newer TC version and new custom column definitons wouldn't work in older TC versions.
A conversion tool or wizard would be a way out of this dillema.
I have suggested this several times to the author...
At least, I hope Ghisler implements some changes to command system or introduce macros, so users can make things like, for instance, "Copy and add to queue" in only one keystroke. Instead of F5 + F2, somebody can select for instance F11. I guess, people is desperating waiting for this... 
