Cheers DJW for your answer. I checked the docs and the behaviour of AddMesh seems a little undefined, as in if ain't documented then you can't rely on it being consistent. There's no mention of a default mesh being created (in the case where one hasn't already), whether by default surface # 1 is used, etc, and clearly no way to specify which surface to use (hence sswift's code).
I'm not really concerned at this point what BB does with surfaces behind the scenes (almost a pun) but it does lead to other questions, eg, what happens when I "paint" a mesh? Does it overide all surfaces? Can I restore, ie, unpaint the mesh? Are brushes "sticky", ie, having painted a surface if the brush attributes are changed is the surface automatically changed? I think I know the answers but the thing is that if you forget, and it's not documented, you have to start trawling these forums for answers again and/or start writing little test apps. Both of which detract from coding your app.
I'm not really concerned at this point what BB does with surfaces behind the scenes (almost a pun) but it does lead to other questions, eg, what happens when I "paint" a mesh? Does it overide all surfaces? Can I restore, ie, unpaint the mesh? Are brushes "sticky", ie, having painted a surface if the brush attributes are changed is the surface automatically changed? I think I know the answers but the thing is that if you forget, and it's not documented, you have to start trawling these forums for answers again and/or start writing little test apps. Both of which detract from coding your app.