Feature request for custom columns.

[Sir_SiLvA]

I have found a way for setting the width of the extension column to 0.

Ever tried this? If doin so it look like this for me:
http://img57.exs.cx/my.php?loc=img57&image=customviews8lw.jpg

BTW is it normal that if I have
Left - Long View
Right - Custom View
and Restart TC I have Long View on both Panels...?

[Static]

Yes, I got the same problem when setting the name column width to 0, just as I described in my previous post. It only works without trouble with the extension column.

I don’t have the problem with different views on exit and start-up. When I restart TC, they are the same as before. I wonder why yours isn’t. Strange.

[sgp]

I second the request to be able to copy all columns (tc and plugins) contents to clipboard. That's an area where xplorer² really shines, pity TC can't match it (yet). Someone here implied that you can print columns, that's true but not custom columns AFAIK.

[radeknews]

Hello,
since many file system plugins put their main item info (e.g. service: running or stopped) in the extension column -
I have been trying to get extensions displayed aligned in a custom view.

It seems however, that this is only possible, if they are aligned in the standard views as well.
(But then I find it hard to find out the complete file name, at least as long as the background is plain - without row shading, especially on large screens, so I definitely don't want to do that.)

I tried to work around this by putting an extra column [=tc.ext], but that one showed nothing, which seems like a bug to me...
Is this a known issue?

Regards
Radek

[Lefteous]

2radeknews
Hi,

Filesystem plugins don't support custom columns at all. If you see any additional information there it means that these filesystem plugins use one of the standard columns (date, size or attributes) to display this information instead.
Custom columns for filesystem columns is discussed in this thread:
http://www.ghisler.ch/board/viewtopic.php?t=6580

[Balderstrom]

Not sure if this applies, but perhaps it would be nice to be able to *remove* the extension or even the name column's in custom columns. Those two fields are static and as such disallows you from putting anything in front of the filename even - I don't know if anyone would want to do that, but why not?

[ado]

Not sure if this applies, but perhaps it would be nice to be able to *remove* the extension or even the name column's in custom columns. Those two fields are static and as such disallows you from putting anything in front of the filename even - I don't know if anyone would want to do that, but why not?

yes it was discussed long time ago...shortly after TC came with this feature and I believe ghisler mentioned, that he needs those 2 columns, because they are use as "kind of line identifier".
I personally would just welcome ability to remove those 2 columns

ado

[Clo]

2ado

Hello !

- It seems that at least the name is needed, or else not any column can be displayed, as well for custom columns as for the default sorting-header… Maybe it's caused by the used base-code ?
- Currently, i.e. it's impossible to get an empty header (stupid example, indeed !).
- Anyway, the name is always useful, IMHO…

- Globally, the column-thing needs improvement, so I'm thinking deeply to this with someone else together {very close in that thread }

 Kind regards,
Claude
Clo

[Balderstrom]

Well they may be required, but there shouldn't be any reason why another column can't be inserted before them...
And the ability to hide the "Ext" column could be an option - a checkbox in the custom column definitions - still there for TC's requirements, just not displayed.

[szlori]

I completely agree, that these columns should be hideable.

Even if I completely understand how these columns are the line identificator, I don't understand why they need to be visible.
Internally they will still exist and identify the lines, but the user should be able to hide them.
If then he/she won't be able to identify the line that's his/her problem.
But I seriously doubt this would affect the functioning of TC itself...

[Lefteous]

I think the reason why the name and extensions columns cannot be hidden is based on the experiences with Microsoft shell based programs or in short Explorer. Explorer has an option to hide the extension for known filetypes. The result is that malware has very nice filenames like Nicegirl.jpg.bat. In this case .bat is hidden...
A way around this problem (concerning columns in TC) could be a warning before such files are executed. But this could be annoying when executing "My Program 1.00.exe".
For experts user it could be an interesting option especially when the filename+extension doesn't give any useful information (IMG_1084.jpg) but it's really dangerous!
I agree with Balderstorm that it should be possible to display columns before name+extension but it shouldn't be possible to hide them or insert a column between name+extension.

[ado]

- It seems that at least the name is needed, or else not any column
....
- Anyway, the name is always useful, IMHO…

Claude,
yes and no... I'll be very happy if I can use one column fullname instead of standalone name and extension

ado