Icons from Resources not showing up in QPushButton or QToolButton

[alom]

Heya,
Hmmm... strange, i'm not sure where the issues is. If you not using an alias and only prefix, I would have though the file path should be:

":/icons/Resources/TableEdit.png"

Thats why I use prefix and alias in my qrc file, so my path is always:

":/prefix/alias"

and if you just explicitly set the image path for a test, your the image is defiantly working fine?

toolButton1.setIcon(QIcon(QPixmap("your/local/network/path/plan.png")))

[Oak77]

@alom Well, I would distinguish the file path in the XML file and resource reference in the code. When the inconsres.qrc is compiled into iconsres.py, it doesn't matter what paths are in the inconsres.qrc, as long as the iconsres.py contains the converted binary data (which in my case it appears it does, it looks similar to images when encoded to jason).
So then it's important that the reference from the code is correct to the encoded images. Something might be broken within the encoded iconsres.py file, the reference in QPixMap might be incorrect or something in the GUI object might be set wrong.

Is my line of thinking correct?

Also, do I understand it right, that there are no tools to track variables and objects through execution? I mean something functionally similar i.e. to VS, like mouse hovering over included iconsres.py to see, that it contains objects like "icons/person.png", etc.

[alom]

To be honest i'm not sure, but trying to recreate your example above in a test file at home, where I did not not use an aslias, I had to use

":/icons/Resources/TableEdit.png"

to get the image to show. Not including 'Resources" in the path failed to load it.

Unfortunately this is the extent of my knowledge with resource files

[Oak77]

@alom Oh, that is interesting and very helpful, thank you! It doesn't work for me, though. Could you tell me please, did you do the conversion using:

pyside2-rcc iconsres.qrc -o iconsres.py

?

[Oak77]

@alom I mised your last comment about the direct link to image file. I tested it now and yes, that works well.

[alom]

@Oak77

Heya,
yes I used the snippet I posted in my above post. I save this as a separate .py file where i keep my resources and run this to generate my files. You need to make sure your system path env has acess to pyside2-rcc, else you need to modify the code to point to the pyside2-rcc on your network.

import subprocess
from pathlib import Path

file_path = Path(__file__)
output_file = file_path.parent.parent / Path('guiResources.py')
resource_file = file_path.parent / Path('resources.qrc')
# cmd and sub process to generated new font resource file
cmd = f'pyside2-rcc {resource_file} -o {output_file}'
subprocess.call(cmd, shell=True)

[Oak77]

@alom I still can't make it work. Your way is exactly how I do it, but for the moment I run the command directly as noted above.

I did another test with QLabel:

The imgs.qrc is shown in the screenshot including it's content, one picture (qtlogo.png). Converted this way:

pyside2-rcc imgs.qrc -o imgs.py

Code fractions:

from PySide2.QtWidgets import ..., QToolButton, ..., QLabel
from PySide2.QtGui import QIcon, QPixmap
import imgs
...
        self.pic1box = self.window.findChild(QLabel, "Pic1")
        self.pic1box.setText = "/home/../Test8/qtlogo.png"
        self.pic1box.setPixmap(QPixmap("/home/libor/Coding/Projects/Test8/qtlogo.png"))

        self.pic2box = self.window.findChild(QLabel, "Pic2")
        self.pic2box.setText = ":/img/qtlogo.png"
        self.pic2box.setPixmap(QPixmap(":/img/qtlogo.png"))

        self.pic3box = self.window.findChild(QLabel, "Pic3")
        self.pic3box.setText = ":/qtlogo.png"
        self.pic3box.setPixmap(QPixmap(":/qtlogo.png"))

        self.pic4box = self.window.findChild(QLabel, "Pic4")
        self.pic4box.setText = ":/img/qtlogo"
        self.pic4box.setPixmap(QPixmap(":/img/qtlogo"))

        self.pic5box = self.window.findChild(QLabel, "Pic5")
        self.pic5box.setText = ":/qtlogo"
        self.pic5box.setPixmap(QPixmap(":/qtlogo"))

        self.pic6box = self.window.findChild(QLabel, "Pic6")
        self.pic6box.setText = ":/Resources/img/qtlogo.png"
        self.pic6box.setPixmap(QPixmap(":/qtlogo.png"))

All icons and images shown have the path set directly, not via resource file.

[SGaist]

What version of PySide2 are you using ?

[Oak77]

@SGaist I don't know if this is a proper way to find out, but versions are listed:

> pip install --upgrade PySide2
Defaulting to user installation because normal site-packages is not writeable
Requirement already up-to-date: PySide2 in /usr/lib64/python3.6/site-packages (5.15.0a1.dev1584103015)
Requirement already satisfied, skipping upgrade: shiboken2==5.15.0a1.dev1584103015 in /usr/lib64/python3.6/site-packages (from PySide2) (5.15.0a1.dev1584103015)

[Oak77]

OK, there are example apps that come with PySide2. Now I went into this one, which is using resource file:

/usr/lib64/python3.6/site-packages/PySide2/examples/widgets/animation/appchooser/

...and run it:

> python3 ./appchooser.py
QPixmap::scaled: Pixmap is a null pixmap
QPixmap::scaled: Pixmap is a null pixmap
QPixmap::scaled: Pixmap is a null pixmap
QPixmap::scaled: Pixmap is a null pixmap
QPixmap::scaled: Pixmap is a null pixmap
QPixmap::scaled: Pixmap is a null pixmap
QPixmap::scaled: Pixmap is a null pixmap
QPixmap::scaled: Pixmap is a null pixmap

and I see only white blank window. Could someone try to run this example app and let me know it it is working? I wonder, if it's connected to this issue I'm experiencing with resource files.

[Oak77]

I somehow progressed a bit with the issue. I tried another Python, the virtual environment that I set during some of tutorials. I installed a PySide2 into that venv and when running my test application in that environment, I can see 2 more pictures in QLabels (actualy those which should work).

But what is interesting nad unfortunate, the icons on the QPushButtons still don't work (the 2 that are shown are assigned via direct link, not a resource file). Icons are in different resource file (iconsres.qrc/icons) from the images (imgs.qrc/img), as is visible in the tree depicted in the screenshot.

Also, when I ran the AppChooser example from PySide2 example set, it was working with the venv.

So I did "pip uninstall pyside2" and "pip uninstall shoboken2" and then "pip install shoboken2" and "pip install pyside2", but it didn't help.

I have two conclusions:

1. Something is broken in my system Python. I have no idea how to fix it.
2. There's something wrong with the iconsres.qrc and also with new testres.qrc, third resource I tried to create in the test project. The 2nd resource file imgs.qrc is valid. But I don't know what went wrong, what's the difference between them.

Any advices for further steps appreciated.

[SGaist]

Can you provide a minimal example with all files that allows to reproduce your issue ?

[Oak77]

@Denni-0 Yep, the thing is, that your modified PyQt5 code works on my system Python, but does not work on the virtual environment Python! So the exact oposite of the case of PySide2 version... It gets even more confusing. Obviously on both is installed the same PyQt5 and PySide2 package.

[Oak77]

@SGaist Yep, I created this one. Test12.zip

[SGaist]

Since you gave an alias to each entry of the qrc file, use that allias to access the images.

For example:

self.pic1box.setPixmap(QPixmap(":/icons/qtlogo"))

[Oak77]

@SGaist Tested, wierd results gets wierder. There should be no difference between usage of alias and file name. But guess what - it still doesn't work in my system environment Python, but in the virtual environment Python, it works with aliases, but doesn't with file names!
Just look at the last screenshot (some 5 posts above), where it works both with the alias and the file name, as it should (it's two unscaled QtLogo images on the right).

Now it looks like this: On the left is app run in system environment or in venv using file names and on the right using virtual Python environment with aliases:

By now I know it's not really the code, but this uncertainty and instability is not a hair smaller concern anyway. One cannot deliver reliable app, not knowing what's happening.

I believe it has to be in the Python itself. There must be some difference between the package distributed in OpenSUSE:

> python3 --version
Python 3.6.10
> pip show PySide2
Name: PySide2
Version: 5.14.1
Summary: Python bindings for the Qt cross-platform application and UI framework
Home-page: https://www.pyside.org
Author: Qt for Python Team
Author-email: pyside@qt-project.org
License: LGPL
Location: /usr/lib64/python3.6/site-packages
Requires: shiboken2

...and the virtual environment:

> ~/Coding/Projects/venv/bin/python3 --version
Python 3.6.10
> ~/Coding/Projects/venv/bin/pip3 show PySide2
Name: PySide2
Version: 5.14.1
Summary: Python bindings for the Qt cross-platform application and UI framework
Home-page: https://www.pyside.org
Author: Qt for Python Team
Author-email: pyside@qt-project.org
License: LGPL
Location: ~/Coding/Projects/venv/lib/python3.6/site-packages
Requires: shiboken2

They look same, but there must be a glitch somewhere.

[SGaist]

Sill question but, did you install both using pip ?

[Oak77]

@SGaist The system environment Python is installed via YaST from official OpenSuSE repository. As for virtual environment, I already forgot how I did it (it was according to tutorial), but I think it was like "python3 -m venv venv-name" (so actually based on the system one). From there, everything was done like:

pip install Shoboken2
pip install PySide2

When trying to update:

pip install --upgrade Shoboken2
pip install --upgrade PySide2

...it says they're up-to-date.

I uninstalled Python from my system and then installed it back (the same way via YaST) and then uninstalled both Shoboken2 and PySide2, but nothing helped.

[Oak77]

OK, I found a cause. Not the root cause, but at least how to "replicate" this issue.

I found out, that apart from PySide2 installation using pip command, a totally different intallation is coexisting in my system, which I can see in my YaST software manager, named "Python3-PySide2". When I remove it, the resource files starts to work in my system environment Python.

Interestingly enough, pip3 install/uninstall PySide2 command works without even noticing that system PySide2 package. And if it's removed by pip uninstall, PySide2 programs would claim there's no PySide2 installed. When installed back using pip3 install pyside2, they wouldn't run properly with resource files.

The bad new for me is, that I can't remove this package, because it then removes also some shiboken2-cpython libraries, that are essential to start a FreeCAD. I need this software, so I can't remove the system PySide2. And I don't know what exactly is broken there, so I can't fix it. I might ask in OpenSUSE forums.

One more note - the programs look differently when the system PySide2 package is/is-not inistalled. Like another style sheet is used to render them (dark frames vs. light, small paddings in buttons and textboxes vs. large, etcc).

For the time being, I will have to use virtual environment Python.

[alom]

if possible in you working evn, I have had really nice result using conda instead of pip. It manages all the dependencies out side of python for you. You can quite easily create any combination of python version and qt5/pyside2, plus any other python libs you need for your project. Pycharm even comes with a Anaconda installer, but I keep my separated.

Maybe that can help you manage you envs