Autocompletion should adjust itself after launching a PATCH/ACTION function

[4Luke4]

For example, it should suggest:

• INT_VAR
• RET
• STR_VAR
• opcode
• parameter1
• parameter2
• target
• duration
• timing
• resource
• special
• savingthrow
• savebonus
• power
• match_opcode
• header_type
• match_resist_dispel
• check_globals
• etc...........

[burner1024]

Yes, context-dependent autocompletion is on my mind for the future, but it's one of more advanced features, so can't promise that soon. It has much more use than just LAF/LPF parameters. If you want to help with that, for starters you can list those parameters in the autocompletion db.

Also, you might want to take a look at snippets, these are easy to add and allow to insert predetermined code templates like LAF invocation.

[burner1024]

Did you have a chance to check out the snippets yet?

[4Luke4]

Did you have a chance to check out the snippets yet?

No, not yet...

[burner1024]

Well, those are easy, so it's best to evaluate what can be done with them, and then move on to more complicated scenarios.

[4Luke4]

Well, those are easy, so it's best to evaluate what can be done with them, and then move on to more complicated scenarios.

Yeah, they do seem to be easy, I'll see what I can do... To tell the truth, I'm much more interested into SFO... Did you manage to wrap your head around it? Guess we can either use it as it is or rewrite it from the ground up (what I'm currently trying to do – more or less, but it's not an easy task...)

[burner1024]

What exactly do you want from SFO? You can use it normally. If there's more to it, let's discuss in a separate issue.

[burner1024]

I'm going to close this, since I see very little interest.