oshizelly wrote:I don't understand the meaning of the value "5".
Value 5 simply means 1+4 (value 4 should be added), i.e. TC will both not enter archive on Ctrl+Arrow and put focus onto it.
With default value CtrlArrowOpenArchive=5 TC doesn't enter DOCX/XLSX:
1. On Ctrl+Arrow,
2. On Enter,
3. On Enter on LNK,
4. When I paste D:\1.docx to command line.
In fact, some problems are still exist, TC enters DOCX/XLSX:
A. On Ctrl+Arrow on LNK,
B. On cd D:\1.docx,
C. When path to document passed as parameter (however option /A disables entering),
D. When I paste D:\1.docx to path bar,
E. Have I missed something?
Yes, this option CtrlArrowOpenArchive only handles Ctrl+Arrow on the archive itself, no other cases.
IMHO this improvement is quite pointless, sorry. As for me (and I suppose, that the most users as well) I have never had any problems with handing MS Office documents by Ctrl+Left/Right aroow. This issue is rather marginal.
Yes, this option CtrlArrowOpenArchive only handles Ctrl+Arrow on the archive itself, no other cases.
IMHO this improvement is quite pointless, sorry. As for me (and I suppose, that the most users as well) I have never had any problems with handing MS Office documents by Ctrl+Left/Right aroow. This issue is rather marginal.
I strongly disagree, for me it was a problem.
Using search tool results from Everything / FSE the cursor was positioned inside of the "Archive" and not on the file name itself.
So its not pointless just because you don't need it personaly.
Using search tool results from Everything / FSE the cursor was positioned inside of the "Archive" and not on the file name itself
I have to suggest, that this improvement is some unwilling positive side-effect. If you read the author's remark 2 posts above yours http://www.ghisler.ch/board/viewtopic.php?t=23140&postdays=0&postorder=asc&start=50, you'll see, that this new option "CtrlArrowOpenArchive only handles Ctrl+Arrow on the archive itself, no other cases".
So its not pointless just because you don't need it personally.
Not me personally. I've just pointed to MVV's post with the same opinion. I suppose, that many users share it too.
Well, I don't mean, that this improvement is not good. What I tried to do was to draw Christian's attention to the fact. that it is far not enough to resolve these issues, which we have discussed in this topic, so we hope for further steps in the same direction.
I'd like to chime in here and advocate that a clean and comprehensive solution should be found for the new Office file / archive issue. It is true that this nuisance has become more and more troublesome with more and more office files existing in the .xml format.
IIRC, the problem occurs in the following contexts:
1. Pressing Ctrl-Left/-Right on a .Officex file
2. Pressing Ctrl-Left/-Right on a .lnk file pointing to a .Officex file
3. Entering a path ending with a .Officex file in either of these situations:
a. in the TC command line
b. in the breadcrumb bar
c. when calling TOTALCMD.EXE from Windows to set a new folder / focus for viewing with a path ending in a .Officex file as parameter
d. when setting the path with sendcopydata
Feel free to quote and edit the list if I've missed anything.
From what I've read in this thread, Mr Ghisler has so far offered a solution only for #1 in 8.51 RC2/3.
Of course, there should be a .ini value to switch between this new way of handling .OfficeX files and the way it was before the 8.51 release candidates. From my point of view the new way (i.e. never entering those "archives" except with the Ctrl-PgDn keyboard shortcut) should be the default behaviour as it's what most novice users will want, but I'll be happy either way as long as I can avoid having to press Ctrl-PgUp all the time to move back up from inside the Office "archive" where I didn't want to go in the first place.
29kvD38n6
2petermad
Thanks, it is what I just tried to tell in my previous post, but far not so clearly as 9kvD38n6 conclusion.
Are you agree with me, that the best solution would be to give a user the option to set, that TC should not treat Office 2007 files .X-files as archives at all? With the only exception, when a user directly orders to open such file as a ZIP-archive by pressing Ctrl+PgOn.
TC should not treat Office 2007 files .X-files as archives at all? With the only exception, when a user directly orders to open such file as a ZIP-archive by pressing Ctrl+PgOn.
Yes, thats what I agree on.
License #524 (1994)
Danish Total Commander Translator
TC 11.03 32+64bit on Win XP 32bit & Win 7, 8.1 & 10 (22H2) 64bit, 'Everything' 1.5.0.1371a
TC 3.50 on Android 6 & 13
Try: TC Extended Menus | TC Languagebar | TC Dark Help | PHSM-Calendar
I'm just bumping this to see if - since the issue has been recognized and given some attention with the addition of the "CtrlArrowOpenArchive" .ini option - it would be possible to provide a comprehensive fix for all contexts as outlined above?
Sorry, there was no time to add this to TC 8.51 - it would require quite a lot of changes. Therefore I have added just the most common case. Maybe in a later release.
As I now have two small kids, I haven't been as active a computer user as I was, but the problem outlined in this thread still bothers me from time to time. Hence, I just wanted to ask if anyone has come up with a satisfactory (global) solution or whether users are still putting up with unnecessarily pressing Ctrl-Up a lot to get back up out of those pseudo-archives?
To recap (edited quote):
a clean and comprehensive solution should be found for the new Office file / archive issue. It is true that this nuisance has become more and more troublesome with more and more office files existing in the .xml format.
IIRC, the problem [still] occurs in the following contexts:
1. Pressing Ctrl-Left/-Right on a .lnk file pointing to a .Officex file
2. Entering a path ending with a .Officex file in either of these situations:
a. from inside the TC command line
b. in the breadcrumb bar [Don't use this myself, so not sure if this is still an issue]
c. when calling TOTALCMD.EXE from Windows to set a new folder / focus for viewing with a path ending in a .Officex file as parameter ['/A' command line parameter can be used to prevent this.]
d. when setting the path with sendcopydata
