Hey
@ploggy, apologies for the lateness of my reply but I've been flat out with other commitments for the past month. Laf's code did help but wasn't the entire solution to our woes, so I'll try to get back into WiiUShell tomorrow. For now I mainly just wanted to reply to your last post in this thread. You said:
Unfortunately it's probably not that simple. I haven't looked myself so I'm just presuming from what Laf said, but it seems as though a complete rewrite of the code would be necessary just to get the most basic of missing features working.
It's a common problem in software development; from a user perspective it seems as though features A and B are not linked at all but within the code they are. This is a bad way to write code in the first place, since it causes problems such as this, but nevertheless it happens every day in the dev world for various unfortunate but understandable reasons.
The most prominent reason I've seen is simply lack of time; i.e. users/bosses/other stakeholders are desperate to have the finished product yesterday, so that added pressure leads the devs to do things as quickly as possible, just to get a final product that "works". The trade off is that the project becomes a maintainability nightmare, as we are now seeing with RetroArch for the Wii U...and, incidentally, Wii U Shell as well ;-)
