Fn groups are different in the US and the UK

[FrightRisk]

In the US, Fn 0 is light, Fn1 is Bell and Fn 2 is horn. Usually light and horn are toggle, but Bell is latch. In the UK apparently, Fn 0 is still lights but Fn1 is a sound on/off toggle, Fn 2 is horn long and Fn 3 is horn short (or at least on this person's decoder).

He said he is having a problem with trying to work out the latching and non latching functions when trying to create his own button configuration. He thinks that as soon as he uses any function in that group, F1 (the disable sound function) toggles to off.

The user mentioned that he read the code and saw a comment about F2 that it will turn off after a set amount of time but nothing about the F1,

Another reason to maybe use the new command ;) Are we handling the math for turning on and off things in each function group correctly? Did we make any assumptions that F0-F2 would always be lights, bell, horn?

[FrightRisk]

Is "aria" in btnState = clickedBtn.attr("aria-pressed"); a css type?

I see a timer set, but don't see what we are timing, what the value is, or what will happen when the timer value is reached. Is this where F1 could automatically get turned off somehow? Or does his decoder see a change and reset things perhaps? How are we repeating commands that toggle? In other words, what keeps the bell ringing and the headlight on?

[matt-vdv]

I haven't really touched the functions code, but switching to the new system sounds like a good idea! I will have a little play around at some point and try and investigate...

[ManiAkasapu]

He may need to have change the button Type to TOGGLE. That could be Problem

Just to understand the jargon:

Toggle == Press&hold == Momentary button
Is Latch === Switch ?

By default (Master Map), F1(Bell), F2(Horn) are Momentary (Press&Hold) button.

Users can change the button behavior in Mapping screen:

About the code:
The attribute "aria-pressed" will provide the information about whether the button is pressed or not.

About timer: There is no straightforward way to simulate press&hold in HTML. This timer simulate that. F1, F2 are Press&Hold type by default and they only send command when User HOLD the button.

[matt-vdv]

By the sounds of things, this may be fixed by #51 and #53? Even if it isn't, it may give us a better idea of where things are going wrong...

[ManiAkasapu]

I am still trying to understand the problem.. Any function in the map can be configured to be Press&hold type button or Toggle type button.. So, user can configure however he wants.. All he needs is to create new map and configure According to his needs.. It does not matter it's US or UK..

[FrightRisk]

I think the issue is that the command station itself defaults to handling the F2 differently assuming it is always the horn. In Europe it can be something else. Fred

…

On Fri, Mar 12, 2021, 10:22 PM Mani Kumar A ***@***.***> wrote: I am still trying to understand the problem.. Any function in the map can be configured to be press&hold button or Toggle type button.. So, user can configure however he wants.. All he needs is to create new map and configure According to his needs.. It does not matter it's US or UK.. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#54 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AI36OWCNSQUBRL3DWT37PJ3TDLK7ZANCNFSM4X4TAQUA> .

[matt-vdv]

@FrightRisk Ok that makes sense. I personally don't have sound decoders, so I can't verify this. I will have a look and see if I can find where it is going wrong...

[FrightRisk]

I will look too. Withrottle and NCE automatically set F2 to momentary because it is a horn (but not in Europe apparently so that causes problems) I can see the WiThrottle code in DCC-EX handles F2 differently. Fred

…

On Sat, Mar 13, 2021 at 5:57 AM Matt ***@***.***> wrote: @FrightRisk <https://github.com/FrightRisk> Ok that makes sense. I personally don't have sound decoders, so I can't verify this. I will have a look and see if I can find where it is going wrong... — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#54 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AI36OWEE5R3UYO75Q7M7FADTDNAIJANCNFSM4X4TAQUA> .

[matt-vdv]

@FrightRisk ok. That could be annoying for people with non-sound decoders as these would have lights on F2 I think?