-
-
Notifications
You must be signed in to change notification settings - Fork 24
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
"Advanced Options --> Replace hbmenu on exit" does not work correctly in Version 0.5.0 #66
Comments
The way the option works is that, when enabled, it will first backup a copy of hbmenu in/switch/hbmenu.nro and then copy sphaira in it's place. When disabled, it simply stops doing the above. The issue with option is that it doesn't currently feature a way to restore hbmenu when disabling it. I'll look into how best to handle this. I have thought about displaying a pop up on disable, asking if they wish to restore hbmenu. On confirm, backup sphaira, restore hbmenu, and then exit sphaira to the main menu. |
Is it not possible to simply copy the ‘switch/hbmenu.nro’ back into the SD card root and overwrite the file located there if the option is deactivated again? |
Yes, that is what I suggested I could do. It would need to backup sphaira if needed, as some users may only have sphaira installed as hbmenu, so restoring actual hbmenu would permanently delete sphaira. Exiting after restoring hbmenu whilst sphaira has been launched as hbmenu is needed as it means the romfs mounting will no longer work (the file is gone) and other misc details in the code that would break. |
Perhaps it would be better to select the config folder or the switch/sphaira/ folder as the backup/restore destination, so that someone doesn't get the idea of deleting hbmenu.nro from the switch folder? Edit: |
If the hbmenu.nro doesn't exist, and the user selected the option to restore it, then I would probably show an error message explaining that it wasn't found, and that they can re-download it from the appstore. |
The hbmenu.nro will always remain in the SD card root, as it is only overwritten, either with sphaira or the regular hbmenu. Or am I making a mistake? Ah, I see. You're talking about when a backup is accidentally or deliberately deleted and then an attempt is made to restore it. |
Yes the later (I should've specified /switch/hbmenu.nro 😄). I'll look into adding this today |
Thank you very much, also for this fantastic tool! |
Hi ITotalJustice, |
check the workflow file for how to build it, or look at the build_release.sh |
Excuse me, but I know next to nothing about programming. So far I have always compiled a tool with ‘make’ in a source code folder. CMake is something else and I have absolutely no idea what to enter in the terminal. I have looked at build_release.sh, but I don't know what to do with it. And what is the ‘workflow file’? Can't you just tell me the corresponding line that I have to enter? Edit: |
You can go to the workflows page, select the commit you want (the last one is the first proposed in the list) and there you will find the nro compiled automaticaly when a new modification is done on the project. To compile the sources yourself you must setup Devkitpro with the switch-dev environment, open the Devkitpro terminal and type "cmake --preset MinSizeRel" then "cmake --build --preset MinSizeRel" but in some of my tests compilation of the project on Windows work the first time but make some errors the second time (haven't tested it with the last versions so I don't know if this problem is always present) so I've setuped my environment with wsl and like that it works but it's more complicated. So if you're not a dev prefers to go to the workflows page. |
Signed-off-by: shadow2560 <[email protected]>
@ITotalJustice @shadow2560 Happy new year! To get straight to the point: I am not at all familiar with Github and its possibilities. I don't understand how you can automatically create an nro. Since this is not a minor issue, but a serious error in an option that cannot be undone, I think it would make sense to publish a new version. What do you think? |
It's a new feature, not a bug as explained earlier in this topic, we've also discussed of this in #41. |
Well, at least a restore of the original Homebrew menu is currently not possible. So deactivating sphaira does not work either once you have activated it as standard. Incidentally, it is the only option that does not currently work. If that's not a reason for an update, then I don't know.... One of my suggestions would be to offer the option in the main menu to access the root level of the SD card via B in order to be able to switch to another folder containing apps. |
To access homebrews that are not in a standard path you have the file explorer witch is capable to also launch nro files but yes adding the possibility to display homebrews in a custom path the same way as the HBMenu do it could be a good add, it's a problem witch has been already discussed in an other issue. |
Interesting! I didn't know that it was possible to start homebrews in other locations via the file browser. Cool! |
If this option is activated, it can no longer be deactivated. sphaira is started even though the option has been set to ‘deactivated’ again.
The text was updated successfully, but these errors were encountered: