Re: [scite] Replace dialog feature request
Jürgen Urner: Trying to figure out what you are trying to tell ...error in relacement string, things where changed that where not intendet to be changed ...as I understand it. In this case the first occurrence should be as good as the last. Pretty low chance that the last is an unintentional one. Most of the time if one is wrong all are wrong. I think the last is better to show than the first since it confirms extent of change. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Replace dialog feature request
Neil Hodgson wrote: Jürgen Urner: Trying to figure out what you are trying to tell ...error in relacement string, things where changed that where not intendet to be changed ...as I understand it. In this case the first occurrence should be as good as the last. Pretty low chance that the last is an unintentional one. Most of the time if one is wrong all are wrong. I think the last is better to show than the first since it confirms extent of change. Neil ___ So my guess was right. Just a hint to end this discussion. The price you pay for that thought is a bit high. The dialog does replacement stuff it replaces N occurences. If you need some kind of validation that's an extra feature and second thought. Jürgen ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Replace dialog feature request
Neil Hodgson wrote: Jürgen Urner: Bit puzzeled about the replace dialog currently. When hitting the Replace All button in the replace dialog it jumps to the last occurence replaced. Usually takes me lots of scrolling to get back to where I started ...no idea why the last occurence replaced is of any special interest. People like to see that a command has had the expected effect and the current behaviour shows an example of the changed text. While its fairly arbitrary to show the last replacement it does reassure that the file has been processed. That is what the noise is usually taken for. Maybe most people have a few lines of code they'd like to replace something in. But as as soon as there are a few hundred ringing a bell is a much easier on your eyes than getting jumped to an arbitrary location. And when I am at it, a decent hint on the number of occurences replaced would be quite helpful. I find it useless noise myself but its implemented on Windows. Don't get you - why useless? 9 replaced out of 9 expected. Well done ...no typo. Jürgen ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Replace dialog feature request
Jürgen Urner: That is what the noise is usually taken for. Maybe most people have a few lines of code they'd like to replace something in. But as as soon as there are a few hundred ringing a bell is a much easier on your eyes than getting jumped to an arbitrary location. Ringing a bell is much harder on your ears and concentration. Don't get you - why useless? 9 replaced out of 9 expected. Well done ...no typo. I don't count the number of replacements I'm expecting to be made so a report of 9 replacements is unlikely to give me useful information: how do I know that 9 is the correct number rather than 8 or 10? And yes, I find it very helpful to have an indicator. Replacing is the main purpose of the dialog so why not let everybody know what happend? Because it is detail that is uninteresting in the vast majority of cases. You do know that something was replaced because there is no message saying that the operation failed. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Replace dialog feature request
On Monday 30 July 2007 14:48:44 Jürgen Urner wrote: Usually takes me lots of scrolling to get back to where I started ...no idea why the last occurence replaced is of any special interest. Good point, it is really annoying. My normal use story is: 1) Ah, _there_ is a token i want to replace in the whole document. 2) Marking it. 3) Open the replace dialog. 4) Hitting tab. 5) Hack in the replacement text. 6) Hit the Replace All button. 7) Eh, _where_ i am now. 8) Searching and scrolling. Problem: At Point 7 i loose the mental focus that i had at Point 1. I think Bookmarks are no real solution, because they make an easy task more complicated. Btw. one other little improvement could be: To eliminate the need for Step 4, which means: Set the focus to replacement-text-input-field if the user has selected text in the editor. kind of regards, holger And when I am at it, a decent hint on the number of occurences replaced would be quite helpful. Scite 1.71 Thanks, Jürgen ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Replace dialog feature request
Ups ...so many replies. Didn't ment to start a flame or cause any confusion. Neil Hodgson wrote: Jürgen Urner: That is what the noise is usually taken for. Maybe most people have a few lines of code they'd like to replace something in. But as as soon as there are a few hundred ringing a bell is a much easier on your eyes than getting jumped to an arbitrary location. Ringing a bell is much harder on your ears and concentration. Don't get you - why useless? 9 replaced out of 9 expected. Well done ...no typo. I don't count the number of replacements I'm expecting to be made so a report of 9 replacements is unlikely to give me useful information: how do I know that 9 is the correct number rather than 8 or 10? ..yes, I do know te number of occurences expected most of the time. Code very repetitive. And reading 7 instead of 8 rings my bells reliably. And yes, I find it very helpful to have an indicator. Replacing is the main purpose of the dialog so why not let everybody know what happend? Because it is detail that is uninteresting in the vast majority of cases. You do know that something was replaced because there is no message saying that the operation failed. Just to make my point clear - as I see it placing a little note in the dialog Replaced: 3 (a.k.a ring a bell in the users head) should be much easier on the user compared to sending him down an unknown number of lines just to give proof something happend. Bit of an overkill as I see it. . Jürgen ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Replace dialog feature request
Jürgen Urner: Just to make my point clear - as I see it placing a little note in the dialog Replaced: 3 (a.k.a ring a bell in the users head) should be much easier on the user compared to sending him down an unknown number of lines just to give proof something happend. Bit of an overkill as I see it. Showing the change is more direct than telling the user about it. When I see the changed text in context I can more easily detect that an error was made in the choice of replacement string. Telling me that some number of replacements was made gives me no such feedback. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Replace dialog feature request
Neil Hodgson wrote: Jürgen Urner: Just to make my point clear - as I see it placing a little note in the dialog Replaced: 3 (a.k.a ring a bell in the users head) should be much easier on the user compared to sending him down an unknown number of lines just to give proof something happend. Bit of an overkill as I see it. Showing the change is more direct than telling the user about it. When I see the changed text in context I can more easily detect that an error was made in the choice of replacement string. Telling me that some number of replacements was made gives me no such feedback. Trying to figure out what you are trying to tell ...error in relacement string, things where changed that where not intendet to be changed ...as I understand it. In this case the first occurrence should be as good as the last. Pretty low chance that the last is an unintentional one. Jürgen ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
[scite] Replace dialog feature request
Hallo all, Bit puzzeled about the replace dialog currently. When hitting the Replace All button in the replace dialog it jumps to the last occurence replaced. Usually takes me lots of scrolling to get back to where I started ...no idea why the last occurence replaced is of any special interest. And when I am at it, a decent hint on the number of occurences replaced would be quite helpful. Scite 1.71 Thanks, Jürgen ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Replace dialog feature request
Jürgen Urner schrieb: Hallo all, Bit puzzeled about the replace dialog currently. When hitting the Replace All button in the replace dialog it jumps to the last occurence replaced. Usually takes me lots of scrolling to get back to where I started ...no idea why the last occurence replaced is of any special interest. I think it useful to see how far the replacing goes - but sometimes it would be useful to switch back to the last cursor or better switch off this feature. And when I am at it, a decent hint on the number of occurences replaced would be quite helpful. Scite 1.71 Thanks, Jürgen ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
Re: [scite] Replace dialog feature request
Jürgen Urner: Bit puzzeled about the replace dialog currently. When hitting the Replace All button in the replace dialog it jumps to the last occurence replaced. Usually takes me lots of scrolling to get back to where I started ...no idea why the last occurence replaced is of any special interest. People like to see that a command has had the expected effect and the current behaviour shows an example of the changed text. While its fairly arbitrary to show the last replacement it does reassure that the file has been processed. And when I am at it, a decent hint on the number of occurences replaced would be quite helpful. I find it useless noise myself but its implemented on Windows. Neil ___ Scite-interest mailing list Scite-interest@lyra.org http://mailman.lyra.org/mailman/listinfo/scite-interest
