How do I permanently save window position and width/height dimension?

Comments & Suggestions

How do I permanently save window position and width/height dimension?


mattad 03-01-2006, 18:41

I want to save the window position and the width/height of

NoClone for the next NoClone session (after e.g. restart).

How do I do this?

If this is not possible, please include it in the next release

 

Re: How do I permanently save window position and width/height dimension?


spitfire_ch 09-26-2007, 8:26
I agree, this would be a nice feature, especially to be able to save the width of the individual "Search results" items. I think it's useful to always see the full path of the duplicated files (you want to know where they are located in order to choose which one should be deleted). But this requires to adjust the width of every other menu item (basically make everything else smaller). Instead of having to do this every search, it would be very convinient if the program remembered the last settings.

Regards
- spitfire

Re: How do I permanently save window position and width/height dimension?


iliff 11-15-2007, 6:28
I agree with this. I have to tweak column widths every time the results page displays. It's a waste of time because it's always the same columns that are too wide (such as the first two) and the same columns that are too narrow (mainly file location - as Spitfire says, that's always the key).

Sort of related, how about shortening the location information so that it excludes the part of the path specified in the search. For example, if I search in c:/users/GordonBennet/documents then I don't need each result to begin with
c:/users/GordonBennet/documents.

ยต

Re: How do I permanently save window position and width/height dimension?


grubbyjeans 08-13-2008, 11:22
This feature has been requested a number of times and I have not seen a response from support. Is it being developed.

The necessity of resetting columns after each search greatly slows the use of this program.  I stopped using this version and went back to version 3 because of this issue.


Powered by Community Server, by Telligent Systems