It is easy to find the word being typed, and then find
all instances of that word in the document.
Should I then open up an autocomplete window?
Should it be bound to keys?
My problem with binding it to keys (as per request),
is how do I know the user is done? While they are cycling through matches, DrPython needs to keep track of the root word, and which match they are at.
If they move the mouse, or hit a key other than thos ebound to Find and Complete.... or what? I am concerned about the processing needed to check up on this.
The question is, would it be easier to use the built-in (wxSTC) autocomplete window instead of binding this to a key?
In any case, I expect this to be in the next release, which should pop out soon.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have yet to allow the user to bind it to a key, or add it to the toolbar or the pop up menu.
Now what do you think?
Isntead of ctrl+p or ctrl+n to cycle through the possiblities, you ctrl+p (example, wheatever binding you want), and then use the up or down arow, and hit <ENTER> when you got what you want.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think the organization of autocomplete words should be considered clearly. If one enter some chars and ask autocomplete, the list of candidate words will be very longThe Vim mode is convenience, but the work to achieving it is more harder.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
How should this work?
It is easy to find the word being typed, and then find
all instances of that word in the document.
Should I then open up an autocomplete window?
Should it be bound to keys?
My problem with binding it to keys (as per request),
is how do I know the user is done? While they are cycling through matches, DrPython needs to keep track of the root word, and which match they are at.
If they move the mouse, or hit a key other than thos ebound to Find and Complete.... or what? I am concerned about the processing needed to check up on this.
The question is, would it be easier to use the built-in (wxSTC) autocomplete window instead of binding this to a key?
In any case, I expect this to be in the next release, which should pop out soon.
I plopped it into cvs using autocomplete.
I have yet to allow the user to bind it to a key, or add it to the toolbar or the pop up menu.
Now what do you think?
Isntead of ctrl+p or ctrl+n to cycle through the possiblities, you ctrl+p (example, wheatever binding you want), and then use the up or down arow, and hit <ENTER> when you got what you want.
If we can use the built-in wxSTC autocomplet window that's ok and more easily.
I think the organization of autocomplete words should be considered clearly. If one enter some chars and ask autocomplete, the list of candidate words will be very longThe Vim mode is convenience, but the work to achieving it is more harder.
How is the Vim Mode more convenient?
By my understanding, you use ctrl+n/ctrl+p to cycle through. You can do the same thing here.
All you need to do here is use <Up> or <Down> to navigate. You can even use <Page Up> or <Page Down> to go faster.
I mean in vim mode we don't need to create a list contral to save all matched words, but one word. Not pointing the operation aspect.