I would like my Lister title bar to show not only the full path name of the currently selected folder, but also the name of a currently selected file, like so:
C:\Program Files\GPSoftware\Directory Opus\dopus.exe
How would I go about doing this, please?
You can't do that at the moment, as far as I know.
You can copy the full path to the clipboard at the click of a button, and see it in various other ways in the file display, but there's no way to put the selected file path(s) it into the titlebar; only the current folder paths.
Well, that's a bummer. I tend to create file names that are really detailed (long), but I like to keep my Column Headers at a set width, which cuts off file names. Thanks, Leo!
You could use tooltips to show the full path to the file you're pointing at.
But which situations arise where you need this, and can't easily infer it from the current directory plus the filename? Is it for Find Results?
I have all folders on all drives configured in Details mode, and all Header Columns are set to specific widths and locations (order). Because the column headers are specific widths, long file names are often truncated. I can see their full name in tooltips, but
I have to hover the mouse over a file name, then wait for the tooltip to appear - I'm impatient
The path names in tooltips are often word wrapped. If there was a way to make the tooltip popup window wider, or automatically resize itself to fit whatever part of an infotip is the widest, so information doesn't get word wrapped, that would be satisfactory.
As seen in this screenshot:
three of the file names look identical because their names are truncated. I make many Directry Opus configuration changes, and create many backup .OCB files, all with a pre-formatted name stem, then the date is added to the end, like so:Directory Opus Pro v11.0.2 BETA 2 (build 5102 - 32-bit) Config (12-26-2013 @ 258 p.m.).ocb
Directory Opus Pro v11.0.2 BETA 2 (build 5102 - 32-bit) Config (12-26-2013 @ 1133 a.m.).ocb
Directory Opus Pro v11.0.2 BETA 2 (build 5102 - 32-bit) Config (12-26-2013 @ 1140 a.m.).ocb
If the selected file's name was shown in the title bar, I could instantly determine which file I am selecting. Instead, I see this:
Directory Opus Pro v11.0.2 BETA 2 (build 5102 - 32-bit) Config (12-26-2013...
Directory Opus Pro v11.0.2 BETA 2 (build 5102 - 32-bit) Config (12-26-2013...
Directory Opus Pro v11.0.2 BETA 2 (build 5102 - 32-bit) Config (12-26-2013...
Even if this feature I'm asking for doesn't happen, I'm still buying the upgrade. You have a customer for life.
I don't think full filepaths in the title bar is a good idea. What do you think should be shown when selecting more than one file? I would temporarily enable Autosize for the columns. The advantage would be that you can see the names of all files at once. I couldn't get a simple toggle button working (although this might be possible) but you could use a 3-button (or hotkeys) with Set AUTOSIZECOLUMNS for left click and Go CURRENT for right click to go back to your normal column size.
That's a good idea. Maybe if I select multiple files, then the title bar defaults back to showing just the full folder path. I've actually created a Lister that uses auto-sizing columns and another that displays the folder like all of the others. I had a "well duh" moment: since my Directory Opus backup config files have the date and time in their file names, auto-sizing provided the solution I was looking for. Now if I could get the infotips to size themselves according to the largest item in the tip, that would be nice.
No problem here with your filenames. See screenshot:
It's probably dependend on your screen resolution or windows settings (leo will know that 
) after how many characters the text is cut. In fact my tooltip can show about 20 characters more until it's cut.
Btw: You should Link your account to get priority support.
Taking a step back here, do the filenames really need to be so long?
[ul][li]The build number is never going to be needed.[/li]
[li]The "beta 2" is actually part of the version number (With the Opus 11 version number convention, 11.0.1 is beta b and 11.0.2 is beta 2).[/li]
[li](Config is generally both forward and backward compatible between versions as well, so the version number may not be needed, and almost certainly only the major version if any version at all.)[/li]
[li]They're all from the 32-bit version, and configuration almost never differs between 32-bit and 64-bit anyway.[/li]
[li]The date and times are in the date column, so don't really need full date and time to be in the filename. (And if you do have them, you don't need to see them as you can see the time column.)[/li]
[li]I can't think why you'd need a reminder that the config files came from the Pro version, so the word "Pro" can probably be removed.[/li]
[li]The word "Config" in the names isn't needed as the .ocb (Opus Config Backup) file extension implies they are config files.[/li][/ul]
Almost all of the example filenames, at least, seems unnecessary & could be removed, leaving much shorter names that don't require excessively wide columns or new functionality to view. (And any new functionality that only let you read one filename at a time would still be very poor compared to being able to see all the useful details of all files at once, which you can do already by removing the details that don't matter from the names.)
e.g.
Directory Opus Pro v11.0.2 BETA 2 (build 5102 - 32-bit) Config (12-26-2013 @ 258 p.m.).ocb
->
DOpus 11.0.2 (12-26-2013 a).ocb
(Using a, b, c at the end if you really need to do more than one backup per day, although that's pretty unusual. I'd probably just say "DOpus 11" without the ".0.2" as well but at this stage we're short enough to include some extra info if it seems useful.)
[quote]The date and times are in the date column, so don't really need full date and time to be in the filename.[/quote]When you want to save several Backups to the same path using a button the only way to get it working is to apply the date & time to the name because the Prefs Backup command doesn't accept something like Whenexists=rename at the moment. Probably this could be added. The possibility to easily restore the newest Backup from a given path with the Restore command would also be nice to have.
Those filenames in the examples are not coming directly from the Prefs Backup command, they're being renamed afterwards, so I don't think that is relevant.
If you want automated backup and restore with esoteric behaviours (e.g. special file naming/numbering, or auto-restore the most recent config backup), you can do it yourself now with the scripting support in Opus 11.
Yeah, not a big deal. I only do several backups/restores at the same day when I heavily play around with Prefs, button codes and Layouts/Styles which is the case since DO11 beta is out. My "restore last backup" button works fine with the "SelectNewest" script example.
[quote="leo"]Taking a step back here, do the filenames really need to be so long?
[ul][li]The build number is never going to be needed. - I was including it in the names of my backups so I would know exactly which version of DO I used to make that particular Config file, in case future builds change the Config format, through a bug or intentional changes. After all, BETA 2 did come out only one day after BETA 1 due to bug fixes.[/li]
[li]The "beta 2" is actually part of the version number (With the Opus 11 version number convention, 11.0.1 is beta b and 11.0.2 is beta 2). - The tooltip for the tray icon still says "Directory Opus 10" which kind of puzzled me. I was not aware of the particular naming convention used to describe DO 11 builds (it's not documented, as far as I know).[/li]
[li](Config is generally both forward and backward compatible between versions as well, so the version number may not be needed, and almost certainly only the major version if any version at all.) - "generally" "may not" "almost certainly" The version 11 BETAs have a lot of new features that 10.5.4.0 didn't have, so trying to restore a backup from the older version to DO 11 might break my settings.[/li]
[li]They're all from the 32-bit version, and configuration almost never differs between 32-bit and 64-bit anyway. - "Almost never"[/li]
[li]The date and times are in the date column, so don't really need full date and time to be in the filename. (And if you do have them, you don't need to see them as you can see the time column.) - It is a lot easier and faster to determine when a backup Config was made by having it in the file name, rather than clicking on a file, then looking over at the Date column. The only date column I have showing in my Lister is the Modified column since I don't care about when a file was created, just when I last modified it. If I create a file but never modify it afterwards, the Created and Modified dates will be the same, so I don't need the Created column to be shown.[/li]
[li]I can't think why you'd need a reminder that the config files came from the Pro version, so the word "Pro" can probably be removed. - The "Light" version lacks a lot of features of the "Pro" version, so using a Config made by the Pro version when using the Light version might not work. My point is, I try out a LOT of software, so I need to keep track of settings between different versions of the same products.[/li]
[li]The word "Config" in the names isn't needed as the .ocb (Opus Config Backup) file extension implies they are config files.[/li][/ul]
Almost all of the example filenames, at least, seems unnecessary & could be removed, leaving much shorter names that don't require excessively wide columns or new functionality to view. (And any new functionality that only let you read one filename at a time would still be very poor compared to being able to see all the useful details of all files at once, which you can do already by removing the details that don't matter from the names.)
e.g.
Directory Opus Pro v11.0.2 BETA 2 (build 5102 - 32-bit) Config (12-26-2013 @ 258 p.m.).ocb
->
DOpus 11.0.2 (12-26-2013 a).ocb
(Using a, b, c at the end if you really need to do more than one backup per day, although that's pretty unusual. I'd probably just say "DOpus 11" without the ".0.2" as well but at this stage we're short enough to include some extra info if it seems useful.)[/quote] I make several backups everyday since I am experimenting with different DO settings. Sometimes the changes I make are very minor, but are different enough that I want to be able to backup and restore previous settings if I make a mistake. If I know when I made a backup, I can remember what changes were made. Labeling a backup with a, b, c, etc. is not descriptive enough for me. Anyway, I have taken your advice and shortened the names of my backups to more reasonable lengths.
From another comment you made (Leo): "Those filenames in the examples are not coming directly from the Prefs Backup command, they're being renamed afterwards, so I don't think that is relevant.
If you want automated backup and restore with esoteric behaviours (e.g. special file naming/numbering, or auto-restore the most recent config backup), you can do it yourself now with the scripting support in Opus 11."
I am formatting my backups' names using a script that you and another user (steje) told me about - this one:
@nofilenamequoting
Prefs BACKUP=all TO "{s}Administrator - Opus Config ({date|MM-dd-YYYY} @ {time|hh;mm tt})"
Everything is a question of organization 
. There's an easy rule I've learned since my first computer (Amiga): Large names require large columns and large resolutions/monitors . So always try to use short names or use the smallest readable font.
Do you really remember exactly each change in the last 10 configs without an additional "changes.txt" (that btw. would shorten the filename by using version-numbers)? I can't imagine that. And it doesn't make sense to me to backup more than 2-3 configs - each config includes other changes and if you want to combine them at the end, how do you realize that (e.g. you did 10 changes, but want a color-value from an older config, you need to backup, restore from older, copy the value, restore the new config, change the value and save it again to a newer)? And on set up "default/common" settings: Either I want to delete to trash or not, either I want full row selection or not. And such settings you can easily change everytime.
Sure, I also spend much time on configuring and my actual config is the result after hundreds of hours, but at least I bought DO because I want to work with it and on too many (big) changes I never get used to it (e.g. button-/toolbar-arrangement, lister-views,...)! I agree that it is not easy to restore big changes and organizing them. But DO offers some ways to do that with one config: Buttons can be stored as usercommands, same with scripts or toolbars/sets, layouts and so on. And you can store settings, that can't be saved within config, in a text file (e.g. I saved statusbar-codes or the optimal columns-width for each resolution/device in OneNote).
I've already made changes that were suggested, so this thread can now be put to rest.
