Alright, thanks a lot! Planning to add elif after this commit makes it into master. labelsel is also in grasp.
And, maybe the recursive for can be a thing, too. A word of warning for that, though. There is basically no system in existance that can do dir recursion to an unlimited depth. It will be enough so that the limit is not reached on a normal system, though. Unsure what to do when that limit is hit (error message?).
Also,another idea I had - you disabled preview in your scripts, leaving the upper screen in the ugly "preview off" state. What about being able to customize the text there, or even display graphics from a PCX image instead? I'll still need to look into the possibilities (PCX may again mean a slowdown), but is that something you'd use?
Well, I've tried the latest versions of my scripts, including the ones for the two installers. I have added more if nesting to include most of the
filesel,
find, and
ask commands since I last compiled them (I also added a Friends save backup option to the Activity Log Manager, so, it's the Activity Log & Friends Manager now -- it only had 6 options, and it's a one digit difference from the location of the PTM save, so, it just seemed like a natural fit). Even with all that extra nesting, I'm not seeing any issues. Everything seems to be working correctly, and the jumps occur practically instantly. I think it's good to go.
I disable the preview because it shows even the parts that aren't getting run. The preview is great for pinpointing typos, but it shows every comment, every ERRORMSG, and now every potential branch-off, relevant or not. A nice centered app title would be an improvement (especially with the option to pick font and size). For that matter, a blank screen would be better than the current message. It almost makes it look like I'm trying to hide something. I just don't want people getting distracted or confused by comments, error messages, and skipped lines. Though speed also became a factor when I started merging things.
Images might be nice, but I don't want to slow things down noticeably. Also, I am not really known for my artwork skills (but you can give me a tape that's mostly hiss, and what you get back will sound like a studio recording). I asked Eix about making some splash screens since you've switched to .pcx now, but I haven't heard back yet. If any graphic artists out there want to design some splash screens for my SSRs and/or the swap card, it would be greatly appreciated.
Sorry, by native I meant without scripts. I.E. select your backup, and there is the Restore SysNand (Safe) and the Restore SysNand (Full). I understand scripts for making backups, but if you can do a safe restore of SysNand without scripts then why not a full restore? I hadn't realized that GM9 couldn't distinguish SysNand from EmuNand in backups, so I suppose that you should scrap that, since going simply by name is not the best idea.
Also, is it possible to install 'standard' sighax? Are there any advantages? Sighax.com is down so, I can't figure anything out.
I could make you a version that will only restore backups to where they were taken from. As d0k3 said, though, there are no genuine differences between the two. Just as there are no genuine differences between an audio-only .mp4 file and an .m4a file. I didn't do that by default because some people might want to transfer from one to the other. Still, it's only 3 lines to change (the ones with "*nand_???.bin" -- all they would need is an "emu" or "sys" after the star).
Also, an exploit by itself does nothing. The B9S bootloader did expand on the original exploit by adding an additional exploit that provides further elevated access. I think what may be confusing you (and many others) is that this exploit was never really given a proper name (if anyone wants to start a vote to name it, I nominate "StrapHax"). I apologize if my switch to generalizing as Sighax had something to do with it. But it seemed like it would be even more confusing to keep referring to it as B9S with that no longer being the only bootloader available. As far as I know, GM9 and Luma are using the unnamed exploit as well, so, there's no "Sighax-only" payload for you to try if you wanted to (you would have to patch a CFW and install it manually, and it may not work, since most CFWs expect the full StrapHax environment).
That's a dumb thing to do when you could just do
Code:
ffmpeg -i <input file> -f rawvideo -pix_fmt bgr24 -vf transpose=1 <output file>
without relying on any web service... just sayin'
The whole point of PCX was to save space on the initial RAM disk, and I suggest everyone to do the same - in any case, I could add support for multi plane PCX files, even if their compression isn't the best it's still better than having raw framebuffer dumps.
I hear you (or should I say, I read you
). I like how the switch to .pcx has reduced the size of GM9 builds. Having a more commonly-used format is nice as well, of course. So, thanks for that. I want my SSRs to look nice, but I don't want them getting too bloated. So, if I was going to consider animations, they'd have to be small and have a minimal impact on performance.