Forum Discussion
PIN Entry Not Working
The variable PinIndex_3 is missing. Also PinIndex is missing for slide 5.5 and PinIndex_2 for the question in the quiz. To fix create the 3 variables named as above (number, default value 1).
Why do you need a "bullet point font"? Just use character 25CF (●) from the Unicode version of a standard Latin font.
Fair point on the font, there's no such thing as a "bullet point font", it's just a character, and virtually any standard Latin font includes one. The code isn't there for the glyph, though, it's there for the input logic. SL has no native masked PIN entry, so the JavaScript is what decides which of the six boxes fills next, bumps the index along and handles backspace. Doing that with built-in triggers would be something like sixty odd conditional triggers across the keypad! The script already does exactly what you're suggesting, it types a plain bullet character into a text variable. One caveat on 25CF specifically, agreed it's the better-looking dot for a PIN, and it's a one-character swap in the trigger. But SL subsets embedded fonts to the characters used at design time, and 25CF doesn't appear anywhere in this project's authored text, a glyph injected purely at runtime can fall outside the subset and fall back (or render as tofu).
I was not arguing with the excellent solution, just wondering about the idea of needing a specific font for bullets.
... and I just figured it out.
The idea was to have a font that consists entirely of the same bullet character, so if the user types 47890, it would appear as "●●●●●".