Being able to code isn't genetic, it's a learned skill.Again, you're being awfully prejudistic assuming anyone and everyone can code.
Being able to code isn't genetic, it's a learned skill.Again, you're being awfully prejudistic assuming anyone and everyone can code.
Her name on github is the same as her username here, I don't see where the "transparency" issue comes from.
At this point. The argument seems that you can't disable, or "toggle" rosalina. But by definition, the button combo IS a toggle, so what, you want a toggle for a toggle? Or just make the button combo near impssible to even press, there, you disabled the toggle, and can re-enable it just as easy as if you had a config option to toggle. Problem solved, by the user.
Why is the fact the menu is there such an issue? Why do you hate the fact it exists sk much? Not being able to open it by a button combo is literally no different then no button combo. Rosalina has been explained as to why it needs to exist as it is, but a hard/invalid button combo is the same thing as it being removed, and the best part is, that is a user choice to do and fix and mot forced upon devs to do.
Thanks Squall I didn't know that.Being able to code isn't genetic, it's a learned skill.
Gonna play devil's advocate here, even if he did know C, I wouldn't guess he could just jump into forking and editing this in. A CFW isn't three files that work off each other, it's huge (or atleast it looks huge). I guess he would have to understand some of how the 3ds listens to buttons.Being able to code isn't genetic, it's a learned skill.
But it doesn't give the user the choice to disable the menu entirely.
That's what I'm doing for now. Especially given the reaction I've received from this thread. I didn't think there'd be such a defensive stance about Rosalina.Don't want rosalina, but still want luma?
Use a version of luma that does not have it, that be one of the older versions.
I don't know about that. I haven't done any work on the Luma3DS code base, but I found the relevant functions in a few seconds.Gonna play devil's advocate here, even if he did know C, I wouldn't guess he could just jump into forking and editing this in. A CFW isn't three files that work off each other, it's huge (or atleast it looks huge). I guess he would have to understand some of how the 3ds listens to buttons.
What about it being invalid? It's waiting for absolutely nothing, it knows nothing can trigger it. We just supplied a perfect answer that fits your problem but you want it to be official. What is it about the menu you hate so much? If you want this to stop, describe why you hate the menu SO much in perfect detail, no TL;DR form, in like a paragraph or two.Exactly that.
Setting the combo to [literally every button] doesn't disable the menu, it's still listening for [literally every button]. I just want to be able to disable opening the menu.
It's because the menu uses an infinitesimal amount of CPU time polling the input buttons, which could otherwise be used by the game for 0.00000019284 fps improvement. I assume that he also uses a hand-tuned custom-compiled Linux or BSD system that runs zero unnecessary processes, because that's the only possible reason I could see someone caring about something like this.What about it being invalid? It's waiting for absolutely nothing, it knows nothing can trigger it. We just supplied a perfect answer that fits your problem but you want it to be official. What is it about the menu you hate so much? If you want this to stop, describe why you hate the menu SO much in perfect detail, no TL;DR form, in like a paragraph or two.
It's not though. It's still looking out for the 'absolutely nothing' input. Why is this idea so hard to grasp?What about it being invalid? It's waiting for absolutely nothing, it knows nothing can trigger it. We just supplied a perfect answer that fits your problem but you want it to be official. What is it about the menu you hate so much? If you want this to stop, describe why you hate the menu SO much in perfect detail, no TL;DR form, in like a paragraph or two.
But it has literally no affect on the end user. Period.It's not though. It's still looking out for the 'absolutely nothing' input. Why is this idea so hard to grasp?
Settings toggle
Rosalina Menu On = Luma listens out for Rosalina menu keycombo
Rosalina Menu Off = Luma stops listening out for keycombo
It's completely different from setting it to something impossible
And why does it bother you that it looks for it?It's not though. It's still looking out for the 'absolutely nothing' input. Why is this idea so hard to grasp?
So you're saying that let's say a light is possible to light up if pigs become dinosaurs and sail through the sky while singing happy birthday with bad autotune? You're saying it is possible for the light to light up?It's not though. It's still looking out for the 'absolutely nothing' input. Why is this idea so hard to grasp?
Settings toggle
Rosalina Menu On = Luma listens out for Rosalina menu keycombo
Rosalina Menu Off = Luma stops listening out for keycombo
It's completely different from setting it to something impossible
But it does. As I said before, user control.But it has literally no affect on the end user. Period.
It's not though. It's still looking out for the 'absolutely nothing' input. Why is this idea so hard to grasp?
Settings toggle
Rosalina Menu On = Luma listens out for Rosalina menu keycombo
Rosalina Menu Off = Luma stops listening out for keycombo
It's completely different from setting it to something impossible
This is a fucking meme. It doesn't give you any more fucking control than if you don't press the fucking buttons in the end.But it does. As I said before, user control.
It's not exactly the same. I'm saying an option for it to stop listening for the keycombo would be good for the user to have control over.The end result is the exact same, except you're trying to put the onus on the developers instead of the user which is entirely entitled and unfair. If they don't want it in their project, it won't be put in their project. It's that simple. There doesn't need to be any other justification (though many others have been given here).
Judging by this, I assume you use Linux, since it provides more user control than Windows. Since most Linux users know how to program, it should be trivial for you to submit a patch to Luma3DS and implement this feature.It's not exactly the same. I'm saying an option for it to stop listening for the keycombo would be good for the user to have control over.
WHYIt's not exactly the same. I'm saying an option for it to stop listening for the keycombo would be good for the user to have control over.