[Bf-python] Proposed BPyAPI Additions.
Ken Hughes
khughes at pacific.edu
Thu Dec 7 22:04:13 CET 2006
Campbell Barton wrote:
> Joe Eagar wrote:
>> Campbell Barton wrote:
>>> One thing about removing the need for
>>> import Blender
>>>
>>> If your a game engine developer it would not be desirable.
>>>
>>> Maybe we could have 2 contexts.
>>>
>>> Alt+P and menu scripts and GE scripts?
>> GE scripts are totally separate anyway. why would they care? I
>> thought we already had two contexts.
>>
>> Joe
> My Bad for this one, looks like it won't adversely effect the GE.
> One other thing
> scn.object.new(obdata)
>
> - Works fine, however what about empties?
>
> Was thinking no obdata for empties, just None.
> empty= scn.object.new(None)
>
> 2 bad points, if any new obkects are added without data like empties, it
> would not fit in (Realisticly this probably wont happen)
> And if the obdata is intended to be a lamp, mesh etc and somehow gets
> set to None, it may be trickyer to debug, then if we
> used....scn.object.new(Types.Empty) - ore some other format.
Wanted to poke this thread; now that we're is BCon2. I just woke up and
realized some of this is in the Scene module now but I don't see epydocs
for it. Tom just assigned a nasty bug to me that would best be fixed by
encouraging users to not use Object.New(), so it would be nice to
document this (the scn.object.new() method) as the "recommended" methods
if we're going to keep it.
Ken
More information about the Bf-python
mailing list