It happened with a lot of another CFW projects in the past, more recently with certain advanced CFWI only noticed after I posted.. But I thought the "attack" was from the devs.. I misread community.
It happened with a lot of another CFW projects in the past, more recently with certain advanced CFWI only noticed after I posted.. But I thought the "attack" was from the devs.. I misread community.
I don't use it, yes. But I want to be able to flat out turn it off.Don't use it then, it's not that bad
You haven't given a single reason why yet.I don't use it, yes. But I want to be able to flat out turn it off.
Why thenI don't use it, yes. But I want to be able to flat out turn it off.
You haven't given a single reason why yet.
Because I don't use it, and I don't want to use it. I want to be able to press any combination of buttons (if need be) without opening up the menu. I want to have the regular 3DS system running with no menu sideloaded or potentially opening.Why then
I don't use it, yes. But I want to be able to flat out turn it off.
Then?> "We don't want menu toggling our project" isn't an acceptable reason why
> "Well why do you want menu toggling in there?"
> "I just don't want it"
>
you won't be able to open it by accident.Because I don't use it, and I don't want to use it. I want to be able to press any combination of buttons (if need be) without opening up the menu. I want to have the regular 3DS system running with no menu sideloaded or potentially opening.
Why is that such a foreign concept though? Why is being able to choose having a menu openable such a bad idea?> "We don't want menu toggling our project" isn't an acceptable reason why
> "Well why do you want menu toggling in there?"
> "I just don't want it"
>
Then put an impossible combination, stop. It's the only way (or just learn C)Because I don't use it, and I don't want to use it. I want to be able to press any combination of buttons (if need be) without opening up the menu. I want to have the regular 3DS system running with no menu sideloaded or potentially opening.
Let's take a look at the inner loop: https://github.com/AuroraWright/Lum...3c95ea/sysmodules/rosalina/source/menu.c#L172why don't you want it to check for the combo?, it doesn't consume any resources and it doesn't affect the performance of the games, you're being irrational.
inner_loop():
push {r4, r5, r6, r7, r8, r9, r10, lr}
ldr r4, .L14+8
ldrb r3, [r4] @ zero_extendqisi2
cmp r3, #0
popne {r4, r5, r6, r7, r8, r9, r10, pc}
adr r7, .L14
ldrd r6, [r7]
ldr r8, .L14+12
ldr r5, .L14+16
ldr r10, .L14+20
ldr r9, .L14+24
b .L2
.L3:
mov r0, r6
mov r1, r7
bl svcSleepThread(long long)
ldrb r3, [r4] @ zero_extendqisi2
cmp r3, #0
bne .L12
.L2:
ldr r2, [r8]
ldr r3, [r5]
bics r3, r3, r2
bne .L3
bl menuEnter()
ldrb r3, [r10] @ zero_extendqisi2
cmp r3, #0
bne .L13
mov r0, r9
bl menuShow(rosalina_menu_t*)
bl menuLeave()
b .L3
.L12:
pop {r4, r5, r6, r7, r8, r9, r10, pc}
.L13:
bl N3DSMenu_UpdateStatus()
b .L4
.L14:
.word 50000000
.word 0
.word terminationRequest
.word HID_PAD
.word .LANCHOR0
.word isN3DS
.word rosalinaMenu
menuCombo:
But what if I need to open it? I can just untoggle the setting. It makes sense to be there as an option.Then put an impossible combination, stop. It's the only way (or just learn C)
open the config with your hex/text editor and change itBut what if I need to open it? I can just untoggle the setting. It makes sense to be there as an option.
But what if I need to open it? I can just untoggle the setting. It makes sense to be there as an option.
That doesn't make sense, especially on a New 3DS, when it could be set to simple toggleable option in the settings.open the config with your hex/text editor and change it
Learn C and add it, nobody'll do this for youThat doesn't make sense, especially on a New 3DS, when it could be set to simple toggleable option in the settings.
So how about adding a 'delete config' to the Luma settings then? So this can all be done on a 3DS?The potential for confusing users outweighs your perceived (solely psychological) benefit. Set it to an impossible combo, and if you need the menu again, just delete config.bin. You've got to reboot anyway. It's just that simple.
Also, this will not be implemented. Period. No ifs ands or buts, no matter what. Sorry, you're just wasting your time.
That doesn't make sense, especially on a New 3DS, when it could be set to simple toggleable option in the settings.
This "reset config" makes a bit more sense, but i still think that'll not be implementedSo how about adding a 'delete config' to the Luma settings then? So this can all be done on a 3DS?
I believe your perception of confusing end users is off. I highly doubt this setting would affect anything, other than give the user more choice.