This might be kind-of related to the open issues about modules (#25 and #1 I think).
Would it be possible to somehow indicate which .bas file is to be used as the 'main' (or master) one, for a given project? So that no matter which .bas is currently focussed in the editor, hitting build/run will compile and run the project rather than the focussed file? I have a series of .bas files which are '#include' into my 'main' .bas file (unhelpfully called playgroundpanic.bas right now but for this kind of functionality I'd be more than happy to change to something canonical and obvious like main or master).
I wondered if you could maybe have a '.cfg' (no name before the extension), in the build folder, as a kind of 'project settings'.
This might be kind-of related to the open issues about modules (#25 and #1 I think).
Would it be possible to somehow indicate which .bas file is to be used as the 'main' (or master) one, for a given project? So that no matter which .bas is currently focussed in the editor, hitting build/run will compile and run the project rather than the focussed file? I have a series of .bas files which are '#include' into my 'main' .bas file (unhelpfully called playgroundpanic.bas right now but for this kind of functionality I'd be more than happy to change to something canonical and obvious like main or master).
I wondered if you could maybe have a '.cfg' (no name before the extension), in the build folder, as a kind of 'project settings'.