It is by design, the autocomplete does not parse include files, only project files. And inside a module you have to convert the include to module, include it outside the module, add it to the project and 'usemodule' for the autocomplete to trigger.
It was requested among other things to improve modules but not implemented.
The include file is parsed for autocomplete if I place it outside a DeclareModule.
For now I used the workaround of copying the relevant declarations into the Module Header till I have finished writing it.
I cannot convert the include to a module, it contains numerous constant and prototype declarations and no executed code.
Well I could do it, but it would be silly, having a empty DeclareModule body. For now my workaround works too.
This should be an easy fix as includes in normal code work, so I hope it is implemented soon.
Because this currently drives me crazy I am placing a bug bounty of 30€ on this.
Will donate it as soon as I get my hands on a PB version where this works.
This is a big oversight... autocomplete must parse include files too. Otherwise it becomes quite bothersome to split code in multiple files... We're all used to autocomplete.