Comments on last beta ;)

[jacky]

Code: Select all

    + CKS dialog: added command "Close Dialog and Trigger Command"

Pretty nice one, well done!

Code: Select all

    + Menu Edit: added command "Select All Files" (Ctrl+Shift+Alt+M). 
      Selects all files in the List, not the folders. 

This one might be useful, but it sure did make me go about an old wish on mine, than I would really enjoy (even as a CKS/Misc feature) which would be the ability to move into view (can be set focus, then move focused item into view, not important) the first folder on List, or first File on List.

It could be two commands, one for Folder and one for File, or only one using the "other kind" compared to the focus item.
The idea would be:
- when going to a folder with many subfolders, being able to easily/quickly "go to"/move into view the first file on List (without having to manually scroll down all the way...) ; or,
- when sorting by date/size, being able again to easily/quickly go to/move into view the first folder on List (without....)

Seriously, I do such things many times a day and I'd love to have only one click to do instead of all those scrolling (even though the mouse wheel is a pretty awesome little thing)

Code: Select all

    * Menu View | Columns: "Define Current Column Widths and Sequence as 
      User Default" is now called "Define Current Column Setup as &User 
      Default" and includes the columns' visibility. 

Sweet! Thanks for this!

Code: Select all

      And, instead of a nagging message box you now get a feedback on 
      the statusbar. 

You know what, I think it might be better if it beeped too. Because right now it can very easily be seen as a "nothing happened" kinda situation, if you didn't expect the statusbar to be the place to look for a confirmation of success.
A little beep, despite being noticable even when Auto-Refresh in on & there's activity on the current location, or if one selects/unselects something, also has the advantage to make the user aware that something happened (which could also make him look down to the statusbar).

[admin]

It could be two commands, one for Folder and one for File, or only one using the "other kind" compared to the focus item.

Now which of both? You decide because you use it several times a day, not me

About the beep, I'd like to hear some opinions of others...

[jacky]

It could be two commands, one for Folder and one for File, or only one using the "other kind" compared to the focus item.

Now which of both? You decide because you use it several times a day, not me

Well... you could always do the 3
I thought about it, I think (for me) the single command using focused item to know which to put into view would be best. When changing sort order I can just call it twice, or change the focused item right before. IMO that'd be better than having two different comands to use...

Using only one command might complicate its "labelling" though... "Moved first folder(/file) into view" is cool, but for the one command, I'm not even sure how to call it

[jacky]

Code: Select all

    * Menu View | Columns: "Define Current Column Widths and Sequence as 
      User Default" is now called "Define Current Column Setup as &User 
      Default" and includes the columns' visibility. 

Ok, going through this again, I now believe this was a bad idea!

Seriously though, since you went there, maybe "Restore Column Sequence From Factory Default" should become "Restore Column Setup From Factory Default" and behave accordingly, no?

[admin]

Code: Select all

    * Menu View | Columns: "Define Current Column Widths and Sequence as 
      User Default" is now called "Define Current Column Setup as &User 
      Default" and includes the columns' visibility. 

Ok, going through this again, I now believe this was a bad idea!

Seriously though, since you went there, maybe "Restore Column Sequence From Factory Default" should become "Restore Column Setup From Factory Default" and behave accordingly, no?

Well I think "Restore Column Sequence From Factory Default" is a bloat and should go home to bloatville. Or, at most, go to the the land of the Miscellaneous. Any objections?

[j_c_hallgren]

Beeping: As long as it can be disabled via some method by user (even "tweak"), I think it would be fine..

Move other type item in view: This is one of those "duh, why didn't I think of that!" things! When using a touchpad (thus no wheel), and having IP showing with only about 10 items in view, this could prove quite handy, IMO....but what to call it? Hummm...

I do believe that a toggle type function might be easiest to use...maybe "Switch focused item type (file/folder)" as label?

Restore col setting: I'd keep it in, but move it out of mainstream as it's likely a command used only on occasion...

[jacky]

Well, yeah you can move it away to Misc. Truth is, I don't think any users aware of those features will ever use it, most likely they'll save their own column setup.

But, for new/unaware users that might be looking for/need such a feature, to only find those related to user setup, when they didn't know about it & therefore haven't saved any... well, they won't think to go look into "Misc" I think.
So maybe, when using "Restore Column Setup From User Default" but there are no User Default, how about a popup not only informing the user but also asking if the Factory Default Setup should be restored instead then, that might come in handy?

[j_c_hallgren]

So maybe, when using "Restore Column Setup From User Default" but there are no User Default, how about a popup not only informing the user but also asking if the Factory Default Setup should be restored instead then, that might come in handy?

Sounds like a good solution to me! Given that a new user might have totally mucked up their settings in learning/trying various features and want to reset it back to original to try again...

[admin]

So maybe, when using "Restore Column Setup From User Default" but there are no User Default, how about a popup not only informing the user but also asking if the Factory Default Setup should be restored instead then, that might come in handy?

Sounds like a good solution to me! Given that a new user might have totally mucked up their settings in learning/trying various features and want to reset it back to original to try again...

Yes, good solution! I would even go one step further and remove the "User" from the two commands...
- Define Current Column Setup as Default
- Restore Column Setup from Default
... and put the factory settings as Default on a fresh installation. That way, no informing/asking popup is necessary.

[jacky]

Yes, good solution! I would even go one step further and remove the "User" from the two commands...
- Define Current Column Setup as Default
- Restore Column Setup from Default
... and put the factory settings as Default on a fresh installation. That way, no informing/asking popup is necessary.

Yeah, sounds good. Though, since the names of those are getting smaller & smaller, maybe add the notion of Mode there too, like "Define Current Column Setup as Default for this(or Browse/Find/etc) Mode" ?

[admin]

Yes, good solution! I would even go one step further and remove the "User" from the two commands...
- Define Current Column Setup as Default
- Restore Column Setup from Default
... and put the factory settings as Default on a fresh installation. That way, no informing/asking popup is necessary.

Yeah, sounds good. Though, since the names of those are getting smaller & smaller, maybe add the notion of Mode there too, like "Define Current Column Setup as Default for this(or Browse/Find/etc) Mode" ?

Yes, would be correct, but I think it will confuse/intimidate new users, and experienced users will know it anyway. So I just leave it short.

BTW: the message box is back (I like it better than a boxless beep) and the box talks about the mode stuff.

[admin]

Using only one command might complicate its "labelling" though... "Moved first folder(/file) into view" is cool, but for the one command, I'm not even sure how to call it

If there's no good name for it it can mean two things: (1) it's nonsense, (2) it's way ahead of time. I'm not sure yet which...

About the functionality: what about any current selections? what about the current focus?

[jacky]

If there's no good name for it it can mean two things: (1) it's nonsense, (2) it's way ahead of time. I'm not sure yet which...

I can guarantee you 110% it's not a nonsense. Therefore, according to you, ....

About the functionality: what about any current selections? what about the current focus?

- don't touch the selection
- well, as I said this feature could first change the focus item, then put it into view. So in that case, that's your answer: focus is moved by that feature to the first item of "other kind"
I think this should be the way it works, especially for cases such as jc mentionned: if you're keyboard driven, there would be no point of moving the view but keeping the focus where it was!

About the name..., "Focus first item of other kind (file/folder)" ?

[j_c_hallgren]

Using only one command might complicate its "labelling" though... "Moved first folder(/file) into view" is cool, but for the one command, I'm not even sure how to call it

If there's no good name for it it can mean two things: (1) it's nonsense, (2) it's way ahead of time. I'm not sure yet which...

About the functionality: what about any current selections? what about the current focus?

Just 'cause we don't have a name for it doesn't mean it's one of the two things you wrote! What about my suggested label? Which was : "Switch focused item type (file/folder)"
It's short and to the point...

IMO, current selections would remain as is...all we're doing is moving focus from where ever it is to the top/first item of the "other" type (file/folder), and putting it into view port.

[admin]

I went for "Switch Focus between Files and Folders".

Should the focus always be on the list after using the command?