On 1/25/13 5:41 PM, Carey Gagnon wrote: > I've been using a splash image for some time without any issues. I just > started playing with dSecurityManager and finally got it working right. > Pulling encrypted passwords from the database and continuing on to the form > if it's good, and exiting if it's bad (after the 3rd attempt anyway). > > While working on all this I had to disable my splash screen because once > the splash screen timeout was done, when the splash closed so did the login > dialog box. > > My app is not hand coded. I am using class designer files and their > corresponding xxx-code.py files. I've called the standard dSecurityManager > which calls the standard login.py file from dabo/ui/dialogs/. (I'll have > questions later about how to call a customized login.py file) > > Anyone else seen this?
The splash screen and the login dialog both display before the main event loop starts, and the login dialog is modal. Something about this combination makes the splash screen become the parent of the login dialog, so when the splash screen is released, the login dialog goes with it. I'll push a commit to the working branch that seems to fix it shortly. Paul _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/dabo-users Searchable Archives: http://leafe.com/archives/search/dabo-users This message: http://leafe.com/archives/byMID/[email protected]
