Comments on Adobe Captivate 3: Simulating a Password Has Never Been So EasyTypePad2009-01-23T01:27:36ZIconLogichttps://blog.iconlogic.com/weblog/tag:typepad.com,2003:https://iconlogic.blogs.com/weblog/2009/01/adobe-captivate-3-simulating-a-password-has-never-been-so-easy/comments/atom.xml/Tim commented on 'Adobe Captivate 3: Simulating a Password Has Never Been So Easy'tag:typepad.com,2003:6a00d8341cdec153ef010536efe7b6970c2009-01-23T04:01:01Z2009-01-23T04:01:01ZTim One of the potential issues with Text Entry fields is the system fonts. Consider the following scenario: Slide 1 :...<p>One of the potential issues with Text Entry fields is the system fonts. Consider the following scenario:<br />
Slide 1 : <br />
1. Blank UserName & Password Field<br />
2. Add Text Entry Box to the Username, making sure to tell the user to press TAB or Enter and using this as the trigger.</p>
<p>Slide 2 : <br />
1. Has the actual username as recorded (remembering to turn of 'show typing')<br />
2. Text entry box over the password - as described in the article. This time leave add the button on top of where the normal system button might be...</p>
<p>The problem here is the font. If the font used in the text entry does not match the system font then the users sees something different. Most Windows apps seem to use MS San Serif, Regular and 10/12 point. By specific systems have their own font style/size. To add the 'bells and whistles' to a professional Cp project its always nice to match these fonts..</p>
<p><br />
If they get it wrong, send them back to Slide 1. The only potential gotcha is that the designer has forgotten to turn off 'retain text' from the properties, and hence the entered text is still there...</p>
<p>Slide 3 : <br />
1. Rest of project starts here</p>
<p>Potentially fiddly to set up, but it is one of the processes that turns a 'good' Cp project into a 'great' one!!!</p>