• minor fix

• use plural for identifiers

In rB2d21eb79ad48485bc7b3385d6df5c2c25fd88ee0#204809, @stephen leger (stephen_leger) wrote:

Any reason for lowercase units enumerator items in python ?

bpy.context.scene.length_unit = 'centimeter'

• recreate batch on every call instead of keeping it in global space

• trying to get a shader without instancing working
• make images visible again

About the Draw API:

ok, when I just disable writing to the depth buffer I get these tow problems:

• fix and cleanup

I think I even tried this and then other things were looking wrong, but I'll check that again tomorrow.

The problem here is not when there multiple image empties but that the mesh selection overlay is hidden behind a transparent image empty.

Looks like the empty image drawn before the mesh selection overlay. Unfortunately I still don't understand how drawing transparent things works when they are not drawn background first... So I don't know how to fix this.

• code style

• fixes

• naming

• use builtin shaders

• more icon and operator updates

Not that I'd need it atm, but is there any reason to have hardmax of 1? Maybe there are cases when people want to make it bigger.

In D3688#88030, @Sybren A. Stüvel (sybren) wrote:

Maybe it would be possible to allow using a batch as context manager? That would allow something like this:

with gpu.types.GPUBatch(type="LINE_STRIP", buf=vbo) as batch:
    batch.program_set(self.shader)
    batch.draw()

That'll also give us a cleaner way to free the batch in case of exceptions, etc.

• better naming

Only happens when the multires modifier actually has subdivisions.

• hide gizmo when image empty not visible

• use a flag

• cleanup

In D3688#87739, @Sybren A. Stüvel (sybren) wrote:

@Germano Cavalcante (mano-wii) what is the purpose of the del batch statement in your example Python code? From what I see it's at the end of the function anyway (the name batch goes out of scope there), so AFAIK the statement doesn't have any purpose.