Thorpy | A GUI library for Pygame | Game Engine library

by YannThorimbert Python Version: Current License: Non-SPDX

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | Thorpy Summary

Thorpy is a Python library typically used in Gaming, Game Engine, Pygame applications. Thorpy has no bugs, it has no vulnerabilities, it has build file available and it has low support. However Thorpy has a Non-SPDX License. You can download it from GitHub.

ThorPy is a free GUI library intended for use with pygame. More informations on

Support

Quality

Security

License

Reuse

Support

Thorpy has a low active ecosystem.

It has 24 star(s) with 4 fork(s). There are 2 watchers for this library.

It had no major release in the last 6 months.

There are 0 open issues and 6 have been closed. On average issues are closed in 42 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of Thorpy is current.

Quality

Thorpy has 0 bugs and 0 code smells.

Security

Thorpy has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

Thorpy code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

Thorpy has a Non-SPDX License.

Non-SPDX licenses can be open source with a non SPDX compliant license, or non open source licenses, and you need to review them closely before use.

Reuse

Thorpy releases are not available. You will need to build from source code and install.

Build file is available. You can build the component from source.

Thorpy saves you 9104 person hours of effort in developing the same functionality from scratch.

It has 18623 lines of code, 1229 functions and 192 files.

It has high code complexity. Code complexity directly impacts maintainability of the code.

Top functions reviewed by kandi - BETA

kandi has reviewed Thorpy and discovered the below as its top functions. This is intended to give you an instant insight into Thorpy implemented functionality, and help decide if they suit your requirements.

Creates a handler for the given variable
Set painter style .
Stitch the rectangle .
make display options setter
Set hover state .
Launch an element .
Blit the surface
Store children of children
Lightweight an alpha surface .
Store rectangles .

Get all kandi verified functions for this library.

Thorpy Key Features

No Key Features are available at this moment for Thorpy.

Thorpy Examples and Code Snippets

No Code Snippets are available at this moment for Thorpy.

Community Discussions

Trending Discussions on Thorpy

Python pygame fails to output to /dev/fb1 on a Raspberry Pi + TFT screen

QUESTION

Python pygame fails to output to /dev/fb1 on a Raspberry Pi + TFT screen

Asked 2019-Mar-04 at 15:16

TL;DR

I am fiddling with a Raspberry Pi 2 and a 2.8" TFT touch screen attached to the Pi's GPIO. The Pi is also connected to a HDMI monitor.
My issue is that my Python3 pygame script is not able to use the TFT screen, but always displays on my HDMI screen instead.

Some background

I've installed the latest vanilla Raspbian ready-to-use distro and followed the TFT screen installation steps, everything works well: the TFT can display the console and X without issue. The touchscreen is calibrated and moves the cursor correctly. I can also see a new framebuffer device as /dev/fb1.

I've tried the following to test this new device:

...

ANSWER

Answered 2019-Mar-04 at 15:16

I have been fiddling around that for far too many hours now, but at least I have found what I'd call a decent workaround, if not a solution.

TL;DR

I've kept using pygame for building my graphics/GUI, and switched to evdev for handling the TFT touch events. The reason for using evdev rather than pygame's built-in input management (or pymouse, or any other high level stuff) is explained in the next section.

In a nutshell, this program builds some graphics in memory (RAM, not graphic) using pygame, and pushes the built graphics as bytes into the TFT screen framebuffer directly. This bypasses any driver so it is virtually compatible with any screen accessible through a framebuffer, however it also bypasses any potential optimizations coming along what would be a good driver.

Here is a code sample that makes the magic happen:

Source https://stackoverflow.com/questions/54778105

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install Thorpy

You can download it from GitHub.
You can use Thorpy like any standard Python library. You will need to make sure that you have a development environment consisting of a Python distribution including header files, a compiler, pip, and git installed. Make sure that your pip, setuptools, and wheel are up to date. When using pip it is generally recommended to install packages in a virtual environment to avoid changes to the system.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: