Release 3.3  Copyright ã1994 by NeXT Computer, Inc.  All Rights Reserved.

3.3 Release Notes: 
loginwindow

This file contains release notes for the 3.3 release of loginwindow. 

Notes Specific to Release 3.3

New Features

The following new features have been added to loginwindow since Release 3.1:

·	loginwindow now has API to allow you to replace certain elements of its built-in functionality: authentication, user interface and screen saving.

·	loginwindow now eats the first event used to clear the screensaver.  This means that if you type a key to clear the screensaver, it won't show up in the username field.

·	loginwindow now automatically logs in usernames with no password set.

·	loginwindow now automatically sets up a few defaults for root and me based on the language selected in the language panel (paper size, 24 hour clock, measurement units, language).

Bugs Fixed in Release 3.3

These bugs have been fixed:

·	There were some instances where the screensaver wouldn't go away if you clicked the mouse button rapidly.

·	The login panel always displayed the hostname of a machine in the panel and in the screensaver even when there's no HostName default.

·	Screen brightness was never set to full brightness on login even if that's what was in the user's default.

·	The power and restart buttons weren't disabled when PowerOffDisabled default is on. 

·	If an alert panel was up when the screensaver kicked in, you couldn't remove the screensaver.

·	If you typed your username and password into loginwindow, but didn't hit return at password yet, then waited for the screensaver to appear, then hit return, you would login, but the screensaver window would cover the workspace.  This could happen accidentally if TimeToDim was a small value.

·	Occasionally, loginwindow would fail to login a user and would print out a message like: ªloginwindow: running /usr/lib/NextStep/Workspace$-40888926º on the console. 

·	loginwindow didn't allow root to login to console when /etc/nologin exists.

·	loginwindow writes out a keymap default for each user if one doesn't exist.  This means that users won't just default to the the machine-specific keymap on each machine they use.