Right I understand, I hope this doesn't come off wrong. Just that when building shared routines/libraries is good practice to distance yourself from the programmer’s main code. it should be all rolled up into a little black box.
The shared functions shouldn't make any requirements on the programmers main code if possible. The programmer should be able to do everything(mostly) through exported functions and not have to rely on changing the guts. Now I understand that Blitz3D holds us back a little here because of it dependencies on globals but the practice is sound and just makes for cleaner routines and programs.
So the reason that the user makes the cameras instead of the routine is because it's the user's program and you never know what they will be doing with cameras or how they will be configuring them. For instance, your routine does not work for the original question in which Akat stated that there were many cameras defined and he wanted to fade between any two.
Those were/are just some suggestions, I didn't/don't mean any offense. :)
The shared functions shouldn't make any requirements on the programmers main code if possible. The programmer should be able to do everything(mostly) through exported functions and not have to rely on changing the guts. Now I understand that Blitz3D holds us back a little here because of it dependencies on globals but the practice is sound and just makes for cleaner routines and programs.
So the reason that the user makes the cameras instead of the routine is because it's the user's program and you never know what they will be doing with cameras or how they will be configuring them. For instance, your routine does not work for the original question in which Akat stated that there were many cameras defined and he wanted to fade between any two.
Those were/are just some suggestions, I didn't/don't mean any offense. :)