search

twinbasic / twinbasic

261 stars 23 forks source link

Replicate VBA IntelliSense behavior in twinBASIC IDE #779

Open mwolfe02 opened 2 years ago

mwolfe02 commented 2 years ago

Is your feature request related to a problem? Please describe. In VBA (not sure about VB6), the autocomplete dropdown does not appear automatically unless there are a clear set of choices to pick from (such as an enumerated type, list of object methods/properties after dot, etc.). When it does appear, the first option is not preselected. No item gets preselected until at least one character is typed. However, once that first character is typed, the autocomplete can be triggered by several other keys (tab, space, comma, dot, etc.).

Describe the solution you'd like Same autocomplete behavior as the VBA editor.

This behavior could not be replicated in VS Code due to the restrictions/limitations of that environment. Is this something that can be revisited for the new IDE? Or is it more of a Monaco editor restriction (which would still apply to the new IDE)?

Describe alternatives you've considered Match the VSCode behavior.

Additional context Having to reach for the up/down arrow key noticeably slows my workflow when working in twinBASIC compared to VBA. I don't know whether that is solely due to my decade and a half of muscle memory or if the VBA approach is objectively more efficient. I'm curious what others think.

Intellisense Taming

v0.10.4966 adds many intellisense tweaks. Most notably, intellisense now won't preselect a partial match. Instead, you'll see the partial text you've entered as the top item in the list:

tb_IntellisenseImplements3

This means that you shouldn't accidently trigger wrong intellisense matches during general editing, and this also helps because we can now turn on SPACE bar support for confirming the intellisense selection, like in VBx (also done in v0.10.4966).

Originally posted by @WaynePhillipsEA in https://github.com/WaynePhillipsEA/twinbasic/issues/337#issuecomment-904684941

WaynePhillipsEA commented 2 years ago

I agree, and I suspect we can work to get this much closer to the VBx offering now.