-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Add functions to Image: static fromqimage and fromqpixmap; methods toqimage and toqpixmap #897
Comments
I think that they'd probably be better off in the ImageQt module. The It seems reasonable to have to/from versions for converting between For better or worse, the current style on to/from is smushed words, not _ words. |
I'm using PyQt for a long time. There is no reason to subclass I understand your intent to separate Qt specific code from anything else. I will put everything related Qt into separate file
|
Looks like this was shipped in 2.7.0 |
It wasn't shipped in 2.7.0: its PR is still open but not ready for merge. |
Thanks |
…thon-pillow#897); fix typo that breaks tests
…thon-pillow#897); fix typo that breaks tests
…thon-pillow#897); fix typo that breaks tests
This change has been merged with PR #1217 and so this issue can be closed. |
I'm writing Qt application that needs diff feature of Pillow
Image
. So, I need to convertQPixmap
toImage
and and vice versa.I've found existing class
ImageQt
. But I don't like it. It contains just one__init__
function. In this case using class is not required. I would say it's misleading.I'm gonna prepare functions for Image class: static
fromqimage
andfromqpixmap
; methodstoqimage
andtoqpixmap
.Those functions would be defined only if PyQt is installed.
What do you think?
PS: I would like to change
from*
functions tofrom_*
due readability. But I want to be consistent. If you likefrom*
more, I would writefromqpixmap
, etc.The text was updated successfully, but these errors were encountered: