On Sun, Jun 2, 2013 at 10:34 AM, Tamito KAJIYAMA <[email protected]> wrote: > I made the "Make Internal" flag optional in the file selection dialog > because I assumed there are users that prefer to use external editors. > Since making a text datablock external requires extra steps, I thought > it would be nicer from users' perspective to be able to opt out the > "Make Internal" operation. > > I am rather neutral about the ways how the "Make Internal" functionality > is made available in Python. Both a .make_internal() method and the > present editable flags are acceptable for me, as I guess this is a marginal > functionality that won't be used so much. > > That said I agree with Sergey that it is nice in general to have a Python API > function corresponding to an operation that users can perform from the UI. > Scripting is much easier if there is a one-to-one correspondence between > the UI commands and Python API functions.
In this case you can just call the operator from the script (which has an internal argument), of if that is a problem add an optional argument to bpy.data.texts.load() _______________________________________________ Bf-committers mailing list [email protected] http://lists.blender.org/mailman/listinfo/bf-committers
