Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Why does the boot image is deformed? #745

Closed
dessant opened this issue May 13, 2016 · 8 comments
Closed

Why does the boot image is deformed? #745

dessant opened this issue May 13, 2016 · 8 comments

Comments

@dessant
Copy link
Contributor

dessant commented May 13, 2016

From @HeaTTheatR on May 11, 2016 7:0

I took the boot image from a folder python-for-android/src/res/drawable/presplash.png. The image size is not changed. Previously, all displayed properly on all monitors, and now like this:

ScreenShot

Ubuntu 14.04 (32-bit), Buildozer 0.33, Kivy 1.9.1

Copied from original issue: kivy/kivy#4276

@dessant
Copy link
Contributor Author

dessant commented May 13, 2016

@HeaTTheatR, previously means in buildozer 0.32?

@dessant
Copy link
Contributor Author

dessant commented May 13, 2016

From @HeaTTheatR on May 11, 2016 12:7

I do not quite understand the question. Yes, earlier I had the version 0.32. Now - 0.33dev.

@dessant
Copy link
Contributor Author

dessant commented May 13, 2016

@inclement, were there any splashscreen changes in p4a recently?

@dessant
Copy link
Contributor Author

dessant commented May 13, 2016

From @HeaTTheatR on May 11, 2016 12:27

Excuse me, I'm from Ukraine, so I can write illegibly. I have not tried to use the standard boot image. I'll be back home, I will tell for sure.

@dessant
Copy link
Contributor Author

dessant commented May 13, 2016

From @inclement on May 11, 2016 18:47

This result is due to a bug in python-for-android, but I thought it was fixed now in both toolchains.

@dessant
Copy link
Contributor Author

dessant commented May 13, 2016

From @HeaTTheatR on May 11, 2016 22:45

It can be fixed?

@inclement
Copy link
Member

@HeaTTheatR Does this still occur, using the master branch of python-for-android?

@inclement
Copy link
Member

I think this is fixed in master following some other issues a while ago, so I'm closing it. Feel free to make another issue or reopen this if I'm wrong.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants