For me, a minor irritant about KFind is, in the Properties tab, when selecting "Find all files created or modified... during the previous..." defaults to 1 hour. Overwhelmingly I want to look for files changed within the last minute or two. I have to pause and manually change the default "hours" list item to "minutes."
Wah, wah, wah!
I want to change that default to minutes.
This default makes sense to me anyway because that is the smallest period in the list.
I already patched KFind for my systems. Should the patch be merged to GIT?
Objections? Arguments? Tantrums? Declarations of War?
Perhaps a better approach is to create a configuration option for the default then everybody could be happy. There is no configuration dialog I know about for KFind. The user's kfindrc is rather sparse and I don't know of any global kfind configuration file. Perhaps KFind should remember the last chosen options in the Properties tab and save them, much like is already done with the file path history.
Darrell Darrell
On 2 April 2012 23:02, Darrell Anderson humanreadable@yahoo.com wrote:
For me, a minor irritant about KFind is, in the Properties tab, when selecting "Find all files created or modified... during the previous..." defaults to 1 hour. Overwhelmingly I want to look for files changed within the last minute or two. I have to pause and manually change the default "hours" list item to "minutes."
Wah, wah, wah!
I want to change that default to minutes.
This default makes sense to me anyway because that is the smallest period in the list.
I already patched KFind for my systems. Should the patch be merged to GIT?
Objections? Arguments? Tantrums? Declarations of War?
I do declare war upon the nature of changing defaults. It is forever unacceptable. Instead we make things customizable. I think your solution below is good.
Perhaps a better approach is to create a configuration option for the default then everybody could be happy. There is no configuration dialog I know about for KFind. The user's kfindrc is rather sparse and I don't know of any global kfind configuration file. Perhaps KFind should remember the last chosen options in the Properties tab and save them, much like is already done with the file path history.
This seems suitable. I really prefer the "remembering" the last settings as apposed to "saving" settings. however my app is left, is how it should come back.
Calvin
On Mon, 2 Apr 2012 23:05:29 -0400 Calvin Morrison mutantturkey@gmail.com wrote:
On 2 April 2012 23:02, Darrell Anderson humanreadable@yahoo.com wrote:
For me, a minor irritant about KFind is, in the Properties tab, when selecting "Find all files created or modified... during the previous..." defaults to 1 hour. Overwhelmingly I want to look for files changed within the last minute or two. I have to pause and manually change the default "hours" list item to "minutes."
Wah, wah, wah!
I want to change that default to minutes.
This default makes sense to me anyway because that is the smallest period in the list.
I already patched KFind for my systems. Should the patch be merged to GIT?
Objections? Arguments? Tantrums? Declarations of War?
I do declare war upon the nature of changing defaults. It is forever unacceptable. Instead we make things customizable. I think your solution below is good.
Perhaps a better approach is to create a configuration option for the default then everybody could be happy. There is no configuration dialog I know about for KFind. The user's kfindrc is rather sparse and I don't know of any global kfind configuration file. Perhaps KFind should remember the last chosen options in the Properties tab and save them, much like is already done with the file path history.
This seems suitable. I really prefer the "remembering" the last settings as apposed to "saving" settings. however my app is left, is how it should come back.
I agree with Calvin on this. Amnesiac applications = bad. Applications that remember what you want = good. And altering defaults is to be avoided unless there is a *really* good reason founded on more than personal preference.
A "make this search the default" checkbox might be the best of both worlds, if we can find room for it in the UI. That would allow a personal search default setup while also giving the ability to clear out elaborate but atypical searches without having to reset each parameter individually. Just leaving it always checked would result in simple memorization behaviour.
I do declare war upon the nature of changing defaults.
It is forever unacceptable. Instead we make things customizable. I think your solution below is good.
Perhaps a better approach is to create a
configuration option for the default then everybody could be happy. There is no configuration dialog I know about for KFind. The user's kfindrc is rather sparse and I don't know of any global kfind configuration file. Perhaps KFind should remember the last chosen options in the Properties tab and save them, much like is already done with the file path history.
This seems suitable. I really prefer the "remembering"
the last settings as apposed to "saving" settings. however my app is left, is how it should come back.
I agree with Calvin on this. Amnesiac applications = bad. Applications that remember what you want = good. And altering defaults is to be avoided unless there is a *really* good reason founded on more than personal preference.
A "make this search the default" checkbox might be the best of both worlds, if we can find room for it in the UI. That would allow a personal search default setup while also giving the ability to clear out elaborate but atypical searches without having to reset each parameter individually. Just leaving it always checked would result in simple memorization behaviour.
I created bug report 955 to address the issue.
I'm changing the defaults for myself.
Darrell
On 04/02/2012 10:02 PM, Darrell Anderson wrote:
I want to change that default to minutes.
This default makes sense to me anyway because that is the smallest period in the list.
I already patched KFind for my systems. Should the patch be merged to GIT?
Objections? Arguments? Tantrums? Declarations of War?
That would be fine with me. If you are searching for anything other than what happened in the last few minutes - you will have to set the fields for what you need anyway. Seems like your proposal covers the most common 'solvable' scenario.
-
Calvin Morrison -
Darrell Anderson -
David C. Rankin -
E. Liddell