I use the password instrument in almost every application I write, and never saw such a problem. I use a more simplistic approach, though, which you could try to check your environment:
1. Since username and password max lenght is not subject to change during program life, I set the corresponding max lenght in the string controls of the login panel
2. I don't try to automatically advance from one field to the next: let the user use the mouse or TAB key instead
3. To use the below discussed approach, all controls on the login panel MUST be set as "Normal" with the exception of "Ok" and "Cancel" buttons
This is the code for handling all login procedure (e.g. in a callback for starting a test):
int ctrl, tmpH = 0;
char msg[512];
// Load the panel and customize password string control
tmpH = LoadPanel (0, UIR, pswd);
PasswordCtrl_ConvertFromString (tmpH, pswd_pswd);
// Install the panel as modal popup
InstallPopup (tmpH);
// Handle user events
while (TRUE) {
GetUserEvent (1, 0, &ctrl); // Wait for next commit event
if (ctrl == pswd_quit) // User pressed "Cancel" button
break;
else if (ctrl == pswd_ok) {
// ** Add code to check username **
errChk (PasswordCtrl_GetAttribute (tmpH, pswd_pswd, ATTR_PASSWORD_VAL, msg));
if (strcmp (password, msg))
MessagePopup ("Warning!", "Incorrect password entered!");
else
break;
}
}
// Remove panel
DiscardPanel (tmpH); tmpH = 0;
if (ctrl == pswd_quit) goto Error;
// The rest of your code here
Error:
// Finalization of the routine: discard dynamic memory, deallocate resources and so on
return 0;
As a last note, avoid calling RunUserInterface and QuitUserInterface more than once i your program: the first one should be called at the beginning of the program to start processing events, while the second only when you want to quit the application. All processing of panels and events can be managed without need to further call of these instructions, which could ingenerate abnormal application behaviour.
