PureBasic Forums - English

Hi,
Please add an option to disable the annoying behavior in Find/Replace Dialog Windows where it always selects the entire contents of Search for:[this] and Replace with:[that] when they receive focus.

If I want to incrementally Replace with:[that1] or [nthat] the darn dialog forces me to unselect all and move around contents twice.

This may be moot if/when Tool automation enables better interaction with all text contents.

What do you mean by "move around contents"?

skywalk wrote:If I want to incrementally Replace with:[that1] or [nthat] the darn dialog forces me to unselect all and move around contents twice.

Just press "Home" or "End" to go the start or end of the selection box. Same as any Windows application.

Trond wrote:What do you mean by "move around contents"?

If I have a series of replacements to make and they only differ by 1 incrementing value...
Then each return to the Replace with:[thatn] forces me to unselect the contents and then re-select what I want to change.
I only want to select a portion of the Search for:[this] or Replace with:[thatn] upon focus!

C64 wrote:Just press "Home" or "End" to go the start or end of the selection box. Same as any Windows application.

Why force a user to use extra keystrokes?
My users scream bloody murder when they are annoyed.
My reply is not "Oh, that's standard Windows behavior...hehehe. Live with it."

My reply is not "Oh, that's standard Windows behavior...hehehe. Live with it."

What if people actually wanted the default behaviour? Not selecting the contents by default get mighty annoying because replacing the value with a brand new one takes a lot of extra keystrokes.

Trond wrote:What if people actually wanted the default behaviour?

skywalk wrote:Hi,
Please add an option to disable the annoying behavior in Find/Replace Dialog Windows where it always selects the entire contents of Search for:[this] and Replace with:[that] when they receive focus.

skywalk wrote:Why force a user to use extra keystrokes?

What? Let's say the requester is showing "Test5" and it's all selected and you want it to be "Test6". All you need to do it hit "End" and then "Backspace", and then type "6". How hard is that? You want them to add an option to NOT select all the text? That's not going to change anything! You STILL have to hit "End", "Backspace" and "6"! No difference in the number of keystrokes at all. I don't get it.

(BTW, this response is based on your comment of want to incrementally Replace with:[that1] or [nthat] where the number being changed is at the start or end of the box).

C64 wrote:

skywalk wrote:Why force a user to use extra keystrokes?

What? Let's say the requester is showing "Test5" and it's all selected and you want it to be "Test6". All you need to do it hit "End" and then "Backspace", and then type "6". How hard is that? You want them to add an option to NOT select all the text? That's not going to change anything! You STILL have to hit "End", "Backspace" and "6"! No difference in the number of keystrokes at all. I don't get it.

(BTW, this response is based on your comment of want to incrementally Replace with:[that1] or [nthat] where the number being changed is at the start or end of the box).

Really? I just gave that as a single example?
Didn't think to list all the permutations of search and replace?

It is frustrating to not be able to mouse select a portion of the field without the requester highlighting the entire contents.

...waiting for advanced tool automation...