[PySide] Help importing compiled Qt resource file from subfolder

[henry.wede at yahoo.com]

 Thank you Adrian.
A typical compiled resource file for me looks like this:qt_resource_data = b"\
{snip}"qt_resource_name = b"\
{snip}"qt_resource_struct = b"\
{snip}
" def qInitResources():    QtCore.qRegisterResourceData(0x03, qt_resource_struct, qt_resource_name, qt_resource_data)
def qCleanupResources():    QtCore.qUnregisterResourceData(0x03, qt_resource_struct, qt_resource_name, qt_resource_data)
qInitResources()

So is the solution from images.compiledresource_rc import qInitResources 

Will that register the resource data without any garbage collection or other problems?
BTW, as much as I love Python, the way it handles modules in folder seems very odd to me.
Henry

    On Thursday, September 28, 2023 at 08:28:36 AM MDT, Alex Strickland <sscc at mweb.co.za> wrote:  
 
  
Hi Adrian
 

 
 
Is that line the same as:
 

 
 
    images.compiledresource_rc import anyFunction
 

 
 
That is, just importing any function will wire up resources like icons etc? I am asking on behalf of a team member, I can't try it myself atm.
 

 
 
-- 
 
 
Regards
 
Alex
 

 
 

 
 

 
 On 2023/09/28 13:34, Adrian Herrmann via PySide wrote:
  
 
 Hello Henry,  
   for your current project structure it appears that this line in helpers.py would be enough for the import to work:  
         from images.compiledresource_rc import someFunction  
   This should work regardless of the working directory, as long as helpers.py is imported from main.py, because the directory that main.py sits in is always added to PYTHONPATH.  
   Let us know if you have further questions or problems.  Best regards,  
|  
|  
  |
|    
  |
|  
  |

  |
|  
Adrian Herrmann
  |
|  
Software Engineer, Qt for Python
  |
|  
|  
  |
|  
  |

  |
|  
Qt Group
 Erich-Thilo-Str. 10 12489
 Berlin, Germany
  |
|  
adrian.herrmann at qt.io
  |
|  
+49 1578 0598682
  |
|  
www.qt.io
  |
|  
|  
  |
|  
  |

  |
|  
Geschäftsführer: Mika Pälsi, Juha Varelius, Jouni Lintunen Sitz der Gesellschaft: Berlin, Registergericht: Amtsgericht Charlottenburg, HRB 144331 B
  |
|  
|  
  |
|    
  |
|  
  |

  |
|  |
|  
|  |  |  |  |

  |

 
  ________________________________________ Von: PySide <pyside-bounces at qt-project.org> im Auftrag von henry.wede--- via PySide <pyside at qt-project.org> Gesendet: Montag, 25. September 2023 01:00 An: pyside at qt-project.org Betreff: [PySide] Help importing compiled Qt resource file from subfolder 
  Hello, 
  I have spend the last few hours trying to figure this out and now I have to ask for some help. 
  My project has grown to the point where is needs to be more organized, so I am moving modules from one huge folder into subfolders.  I use a resource file in QtDesigner and then compile it resulting in a "something_rc.py".  With the "one huge folder" approach I just imported this file into any module that uses dialogs - this is the only way that the images would show up in the widgets.  Now I am struggling to do this with the folder structure. 
  I made a simple example that shows the issue.  The tree is below and the attached zip file contains everything. 
  pkg │   main.py │   test_local.py │ ├───images │       compiledresource_rc.py │ └───utils         helpers.py         util.py         __init__.py 
  
  Briefly, main can import test_local and util without any problems.  The issue is that if helpers needs to import the compiled resource file compiledresource_rc.  I swear that I have tried the exact syntax from different Internet resources and I cannot get it to work. 
  Can somebody please help me deal with this resource file? 
  Thank you for your help, Henry 
  
  
  
  
  _______________________________________________
PySide mailing list
PySide at qt-project.org
https://lists.qt-project.org/listinfo/pyside _______________________________________________
PySide mailing list
PySide at qt-project.org
https://lists.qt-project.org/listinfo/pyside
  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.qt-project.org/pipermail/pyside/attachments/20230928/f1ee465c/attachment-0001.htm>