Homebrew COMPLETED NRO Asset Editor

  • Thread starter Thread starter vgmoose
  • Start date Start date
  • Views Views 32,548
  • Replies Replies 31
  • Likes Likes 41
I'm running into an issue trying to edit LaiNes, I wanted to add an Image to clean up my Homebrew Menu, but whenever I load LaiNes into the Asset editor it seems to screw up the UI, anyway around this?

ScreenShot_20180524062319.png
 
I'm running into an issue trying to edit LaiNes, I wanted to add an Image to clean up my Homebrew Menu, but whenever I load LaiNes into the Asset editor it seems to screw up the UI, anyway around this?
Yeah that's doing my head in too. It must be a non-standard format or something.

Here's a fix for this. Right now it's just cropping and forcing it to 256x256 icons since that's what hbmenu recommends. An NRO could have larger dimensions than that however, so ideally being able to choose the size is probably best in the future.
 
Some NROs won't allow editing; for example, the Genesis Plus GX LibNX RetroArch core, or the latest Beetle-PSX core. This happens even when I use the 256-forced-version.
This is what I get from the console:
Exception in Tkinter callback
Traceback (most recent call last):
File "tkinter\__init__.py", line 1699, in __call__
File "maker.py", line 218, in browse
File "site-packages\PIL\Image.py", line 2585, in open
OSError: cannot identify image file <_io.BytesIO object at 0x028F3750>
 
great app what we need is a proper unofficial switch sdk that handles all this and can make .nro files
 
For anyone interested, here is my piggy-backed fork of this OCD soothing tool <3

I made this because I have issues, and sometimes I reaaaaaaaaaaally dislike clutter. It's totally useless and a waste of time, because a tool should ideally save you some time. This just creates more work, even if it optimises that work.

Anyway. I wanted to change version numbering in some OVL files as well, because I like my Tesla Overlay Menu clean and tidy: https://github.com/HenryBaby/nro-ovl-asset-editor
 
Looks good to me! I also like that you used QT instead of tkinter because if one UI doesn't work on an OS, then users can try the other one.

Also totally agree, organization is so important for this kind of stuff! Even if it's technically more work, at least it's also self-satisfying.
 
Looks good to me! I also like that you used QT instead of tkinter because if one UI doesn't work on an OS, then users can try the other one.

Also totally agree, organization is so important for this kind of stuff! Even if it's technically more work, at least it's also self-satisfying.
That last part is sooo true!

Also, I'm fairly new to all of this. I hope I was clear with where all the credit goes and all that jazz. Please let me know if I should clarify stuff in any way on the Github page and I'll make the changes. Much love!
 
  • Like
Reactions: lordelan

Site & Scene News

Popular threads in this forum