Perhaps if the docs actualy explained the behaviour of the commands. This is what the docs say about import...
If they actualy explained what happens when you import a file, it might be easier for people to understand what is going on.
That brief and totaly unhelpful sentance tells you nothing of what will and will not happen when you use import. (Aside from "import declarations" :P)
You know you dont always have to try and come up with the "smart" answer. It isn't that much of a stretch (without any knowledge of how the import command works in bmax) to expect modules imported from an import to be accessable. Now with the aid of the more helpful answers from people on this thread, I know otherwise.
Import declarations from a module or source file
(that is it nothing more, nothing less)If they actualy explained what happens when you import a file, it might be easier for people to understand what is going on.
That brief and totaly unhelpful sentance tells you nothing of what will and will not happen when you use import. (Aside from "import declarations" :P)
Why? If you need this, you need to rethink your design, as you'll have an alarmingly high coupling (thus your code will be much harder to maintain).
You know you dont always have to try and come up with the "smart" answer. It isn't that much of a stretch (without any knowledge of how the import command works in bmax) to expect modules imported from an import to be accessable. Now with the aid of the more helpful answers from people on this thread, I know otherwise.