raylib-py 5.5.0

Package release for the C Raylib 5.5

This release was made from the output of another project, as mentioned in #45.

Added

• New functions (refer to raylib's repo for more information):
  GetClipboardImage
IsShaderValid
GetScreenTooWrldRay
GetScreenToWorldRayEx
MakeDirectory
IsFileNameValid
ComputeCRC32
ComputeMD5
ComputeSHA1
SetGamepadVibration
GetShapesTexture
GetShapesTextureRectangle
DrawRectangleRoundedLinesEx
CheckCollisionCircleLine
LoadImageAnimFromMemory
IsImageValid
ImageFromChannel
ImageKernelConvolution
ImageDrawLineEx
ImageDrawTriangle
ImageDrawTriangleEx
ImageDrawTriangleLines
ImageDrawTriangleFan
ImageDrawTriangleStrip
IsTextureValid
IsRenderTextureValid
ColorIsEqual
ColorLerp
IsFontValid
TextToSnake
TextToCamel
TextToFloat
IsModelValid
DrawModelPoints
DrawModelPointsEx
ExportMeshAsCode
IsMaterialValid
UpdateModelAnimationBones
IsWaveValid
IsSoundValid
IsMusicValid
IsAudioStreamValid

Changed

• All functions named Is*Ready in 5.0 were renamed to Is*Valid

Fixed

• Various small tweeks in the binding generator (raylibctbg project) resulted in various small bug fixes in the wrapper code like functions called as methods that didn't consider self to be passed by reference when the param required a pointer.

Give feedback!

raylib-py depends heavily on your usage feedback. If you encounter any bug, please, report it in the issues section. Due to how raylib-py is maintained, bugs tend to be a little hard to find but quick to fix. In any case, you won't be required to look into the code, but simply point out which API is behaving unexpectedly.

Would you like to have a more customized binding for raylib?

Please, take a look at this project: raylibpyctbg

raylib-py 5.0.0.post1

Package release for the C Raylib 5.0

This release was made from the output of another project, as mentioned in #45.

Fixed

• load_font_ex function now loads correctly the font when the codepoints are not specified.

Would you like to have a more customized binding for raylib?

Please, take a look at this project: raylibpyctbg

raylib-py 5.0.0

Package release for the C Raylib 5.0

This release was made from the output of another project, as mentioned in #45.

Added

• More context managers from rlgl module (enable/disable pairs);
• Better type hinting/annotation for arrays;
• Utility functions to create arrays for fundamental types.

Changed

• Functions with omitted parameters now require these to be passed;
• The binding code is far better organized due to a rewrite in the binding generator.

Fixed

• Functions with varargs (TextFormat and TraceLog) work with some reservations (I still don't recommended to pass variable arguments);
• Functions returning pointer as array now cast the value to the proper array type instead of returning lists (like LoadModelAnimations).

Please, refer to C raylib changelog for more information.

Would you like to have a more customized binding for raylib?

Please, take a look at this project: raylibpyctbg

raylib-py 5.0.0b1

Package release for the C Raylib 5.0 Beta 1

NOTE: Stable release is planned to the week of December 1st. This beta will not be uploaded to PYPI.

This release was made from the output of another project, as mentioned in #45.

Please, refer to C raylib changelog for more information.

Would you like to have a more customized binding for raylib?

Please, take a look at this project: raylibpyctbg

raylib-py 4.5.0.post1

Package release for the C Raylib 4.5 Post-Release 1

This release was made from the output of another project, as mentioned in #45.

Please, refer to C raylib changelog for more information.

Fixes:

• Vectors and Matrix duplicated declarations:

  This caused ctypes to make funny complaints, like: TypeError: Incompatible types: Vector2 instance instead of Vector2 instance

Would you like to have a more customized binding for raylib?

Please, take a look at this project: raylibpyctbg

raylib-py 4.5.0

Package release for the C Raylib 4.5

This release was made from the output of another project, as mentioned in #45.

Please, refer to C raylib changelog for more information.

Would you like to have a more customized binding for raylib?

Please, take a look at this project: raylibpyctbg

raylib-py 4.2.0.post2

Package release for the C Raylib 4.2 Post-Release 2

This release was made as output of another project, as mentioned in #45.

Added:

• Custom library loading: load a custom lib binary when importing raylib-py:

  You may add a .raylib file to specify custom binaries to be loaded. How it works:

  • Create a .raylib file with the following contents:

    {
        "win32": {
            "64bit": "path/to/my/custom/win32/binary/filename.ext"
        },
        "linux": {
            "64bit": "path/to/my/custom/linux/binary/filename.ext",
            "32bit": "path/to/my/custom/linux/binary/filename.ext"
        },
        "darwin": {
            "64bit": "path/to/my/custom/macos/binary/filename.ext"
        }
    }

    Omit platforms or architectures you don't want/have a custom binary for; the default binaries will be loaded instead. The file is not inspected for any extra content.

  • Before importing raylib-py, make sure the current working directory points to where .raylib is located in your project.

    If .raylib is found, it will look for the binary path for the system platform and arch and try to load it.

    If the .raylib is invalid JSON, it will fallback to the default binary.

    If the binary is not found, it won't fallback to the default binary.

    No path manipulations like os.path.join(...) are made.

Fixes:

• Fixed some swizzling errors on Rectangle

Known Issues:

• Callback for logging will not work
• Functions with vararg will not work
• Avoid string manipulation functions
• Some examples are broken due to API changes
• For some unknown reason, the 32bit binary for Linux is not available.

Would you like to have a more customized binding for raylib?

Please, take a look at this project: raylibpyctbg

raylib-py 4.2.0.post1

Package release for the C Raylib 4.2 Post-Release 1

This release was made as output of another project, as mentioned in #45.

Features:

• PEP8 naming convention;
• Type hinting (instead of type annotation);
• Structures with functions as methods and properties (like some_vec2.length or some_sound.play();
• Vector{2,3,4}, Rectangle and Color have attribute swizzling (like my_vec4 = some_vec2.xxyy);
• Pretty printing: most structures implement __str__() and __repr__() in a friendly way;
• Context managers: begin_* and end_* functions can be called as context managers;
• Context managers for some structures: Camera{2,3}D, Shader and others;
• RLGL and RayMath functions exposed

Fixes:

• Colors passed as sequences in functions had the red component repeated in the green one;
• Texture structure wrapped without functions as methods;
• Rectangle missing __str__ and __repr__ default implementations;
• Context managers not being included in __all__;

Added:

• Vector{2,3} overload for binary operators +, -, * and / (// not implemented); unary +, -, and abs():
  Operators are supported between:
  • Vectors;
  • Vectors and ints or floats;
  • Vectors and sequences of ints or 'float's,
  • Vectors and Matrixes, for multiplication only.
• Better swizzling for Rectangle:
  When doing swizzling in rects, more attributes become available:
  • c, m as center and middle: x + width * .5 and y + height * .5 respectively;
  • r, b as right and bottom: x + width and y + height respectively;
  • swizzling can include from 1 up to 4 attributes, not only 4 anymore.

Known Issues:

• Callback for logging will not work
• Functions with vararg will not work
• Avoid string manipulation functions
• Some examples are broken due to API changes
• For some unknown reason, the 32bit binary for Linux is not available.

Would you like to have a more customized binding for raylib?

Please, take a look at this project: raylibpyctbg

raylib-py 4.2.0

Package release for the C Raylib 4.2

This release was made as output of another project, as mentioned in #45.

Features:

• PEP8 naming convention;
• Type hinting (not type annotation);
• structures with functions as methods and properties (like some_vec2.length or some_sound.play();
• Vector{2,3,4}, Rectangle and Color have attribute swizzling;
• Pretty printing: most structures implement __str__() and __repr__() in a friendly way;
• Context managers: begin_* and end_* functions can be called as context managers;
• Context managers for some structures: Camera{2,3}D, Shader and others;
• RLGL and RayMath functions exposed

Issues:

• Callback for logging will not work
• Functions with vararg will not work
• Avoid string manipulation functions
• Some examples are broken due to API changes

Would you like to have a more customized binding for raylib?

Please, take a look at this project: raylibpyctbg

raylib-py 0.1.1

New minor release to reflect #1 issue. Since PyPA doesn't allow reuse of file names, a new release must be created.