OK...
TBGL improvement for me would mean to split all those different sections into objects. Like
TBGL.Sprite.<member>...
TBGL.Entity.<member>...
TBGL.Window.<member>...
TBGL.Displaylist.<member>...
TBGL.Matrix2d.<member>...
TBGL.Matrix3d.<member>...
...

where member is a property or method of course.
Even enumerations and/or constants could exist in dot-notation.

And once thinAir knows how to autocomplete when user types a dot, coding will be much easier too. It saves a lot of time if the user gets presented a list of possible options instead of searching through documentation for correct spelling or keyword-order.
Was it

TBGL_GetMouseButtonLeft
or
TBGL_MouseGetLeftButton
or
TBGL_LeftMouseButtonGet
or
TBGL_MouseButtonLeftGet
or just
TBGL_GetMouseLButton...?

Dot-notation + autocomplete would make it easy.
And once we have the correct order we still can check help - without further search - for required parameters.
And of course to have an eye on the logic order in future.
-TBGL first anyway
-Library second ( i.e. Entity, Window, Mouse...)
-[Property], [Sub-properties]
- Method in the end

To read left mousebutton it would mean

If TBGL.Mouse.Button.Left.Get Then ...

or just

If TBGL.Mouse.LButton Then ...

Since .Set is not doable logically from within code as a method but by the users finger on the mouse.

Anyway, thanks for the module, I had lots of fun using it.