Timocop / BasicPawn

BasicPawn - SourcePawn Editor
GNU General Public License v3.0
75 stars 11 forks source link

Separate auto completion for methods and forwards, and add methodmapped functions support #28

Closed GAMMACASE closed 6 years ago

GAMMACASE commented 6 years ago

As for now, enabling Full autocompletion for methods enables autocompletion for both forwards and default functions, and having autocomplete for forwards are fine so you don't need to fill all it's params manually, but having autocomplete for default functions is just annoying, as you need to erase all it's content and write values you want to pass each time. So my suggestion is to make 2 autocomplete options for default functions and forwards. Also add support for methodmapped functions to default functions autocompletion, like Menu.Menu() or Menu.SetTitle() as they aren't get autocompleted

Timocop commented 6 years ago

That feature is obsolete and will be removed in future versions of BasicPawn. Its unessescary realy. I created that feature because back in realy old versions of BasicPawn there was no propper IntelliSense. Now there is and it became quite obsolete. forwards, funcenums, functags, typesets and typedefs still autocomplete even with this feature disabled/removed.

GAMMACASE commented 6 years ago

Uh, I see now, forwards gets autocompleted if you don't write public TYPE before it, is there any possibility to enable forwards autocompletion for parameters when there's public TYPE before it?

here's an example of how it looks like: oqvqizebwe

Timocop commented 6 years ago

The full autocompleation was a bit lazy made. It only checked if the line was empty. Now its more context aware. It will only fully autocomplete if its in no scrope, array, method and preprocesor. Theres no need to write public <type> since the whole line will be replaced anyways.

Preview: 2018-10-13_21-47-59

GAMMACASE commented 6 years ago

Guess it's alright, thanks!