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
Hi Neil
Thank you very much! The api is working now, the backslash was the culprit.
Also thanks for showing me how to use echo in the output plane; I was unaware
of this useful debugging feature. As a matter of intrest: I did
echo $(file.patterns.flash)
echo *.mx;*.as;*.asc
*.mx
sh: *.as:
On 7/31/07, Neil Hodgson [EMAIL PROTECTED] wrote:
How are you going to arbitrate between the current extension's
choice and the history? I commonly make a series of searches with one
mask.
I've thought about that. One method would be to (a) always make unique
insertions into the history and
On 7/31/07, Neil Hodgson [EMAIL PROTECTED] wrote:
Don't really see the advantage over using quotes where needed when
specifying commands.
Fair enough, but the patch isn't very complicated:
In SciTEBase::SelectionIntoProperties() (ScTEBase.cxx, 1213)
insert this code:
//
On 31/07/2007 06:55, Neil Hodgson wrote:
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.
Often it is useless, and I just ignore it, and sometime it is precious
(another visual
On 30/07/2007 14:48, Jürgen Urner wrote:
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
I think we're confident enough for this to be updated. I'll have a
look at the needed changes.
The only concern Nicolas and I had was the problem of 'dead pipes'
that happens when an instance of SciTE goes down in flames. I have
some dead pipe cleaning code but I don't know whether it should go
Philippe Lhoste wrote:
On 30/07/2007 14:48, Jürgen Urner wrote:
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
I have uploaded to:
...
long cancelFlag; /* only one job can be executing at a time, this
should be safe as a public variable of the class */
The cancelFlag is used in both the UI thread and the execution
thread so should be protected. That is why InterlockedExchange is used
in the
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
steve donovan:
The patch involves changing the signature of ExtensionAPI::DoMenuCommand;
in Extender.h around line 30, we then have
virtual void DoMenuCommand(const char *cmd)=0;
The idea of a published extension interface is to give extension
writers a solid basis to work. Changing
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
On 31/07/2007 13:41, Neil Hodgson wrote:
You do know that something was replaced because there is no
message saying that the operation failed.
On the other hand, I am starting to find this message (no occurrences
found) more distracting and annoying than my system of screen flashing
(and
On 7/31/07, Neil Hodgson [EMAIL PROTECTED] wrote:
steve donovan:
The patch involves changing the signature of ExtensionAPI::DoMenuCommand;
in Extender.h around line 30, we then have
virtual void DoMenuCommand(const char *cmd)=0;
The idea of a published extension interface is to
On 7/31/07, Neil Hodgson [EMAIL PROTECTED] wrote:
I didn't want to do it this way since its less useful than having
the constants be available to Lua similar to the way that other
constants (such as SCI_SETZOOM) are made available. Doing this in the
same way as SCI_SETZOOM would add around
Philippe Lhoste:
On the other hand, I am starting to find this message (no occurrences
found) more distracting and annoying than my system of screen flashing
(and ring belling!), because I have to dismiss it before changing my typo...
The No replacements alert could be dropped but new
On 31/07/2007 14:53, Holger Kohnen wrote:
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.
It exists or existed, at least in the Windows version, another thing I
find.replacewith.focus=0On Tuesday 31 July 2007 16:28:44 Philippe Lhoste
wrote:
On 31/07/2007 14:53, Holger Kohnen wrote:
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
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
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
Holger Kohnen:
I tried the setting:
find.replacewith.focus=1
but at least on gtk i see no effect.
This hasn't been implemented on GTK+. I have changed the
documentation to reflect this.
Neil
___
Scite-interest mailing list
steve donovan:
So the IDM_ constants could be put into IFaceTable, and would then be
automatically available. Then GetMenuCommandAsInt() could call
IFaceTable::FindConstant(name). I know this is a little awkward,
because then the script-generated tables in IFaceTable come from two
sources,
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.
23 matches
Mail list logo
