bob@cis.ohio-state.edu (Bob Sutterfield) (01/04/89)
chuck@trantor.harris-atd.com (Chuck Musciano) writes: >5) ...The issue of click-to-type never came up? If click-to-type is > not a user configurable option (which the Open Look team was > considering) I will NEVER user Open Look. The issue came up before the specs were released, because I raised it myself, with strong encouragement to make almost everything a user preference option. It had come up before I mentioned it, but had not been considered serious enough to change their plans. Apparently it still isn't. The Functional Specification (Review Draft, 15 July 1988) Section 14 shows that they gave some thought to user preference configurability. For instance, you can disable gratuitous mouse warping if you like. Perhaps the Desktop Property Window could be expanded with more choices (like click-to-type), with the Factory settings remaining for those who prefer "pure OL". As it stands, 9.1 "Selecting a Window" says that the way to select a window is to click SELECT anywhere in the window background, with an implication (by omission) that this is the only way. 11.2 "Core Keyboard Operations" doesn't even specify "Select" as a required function that must be mapped to the keyboard, so you might have been able to wave the mouse at a window and hit a function key to select it (which would have been at least part way there). But then, if that window weren't selected by mouse entry, how is the window manager to know to which application the function key should be delivered? >6) Another undefined issue: if you have click-to-type set, and click >in a window, does this also set the insert point in text windows? The Functional Spec seems unclear on this point, but perhaps I missed it. Window selection and window content selection are covered in two different sections, with no cross-references that I could find. It's also unclear on whether, when a window is selected and raised, all associated pin-up menus are also raised. 6.4 (page 6-8) says that "the default for each menu... is remembered for all windows running the same application, and is saved across invocations of that application." Perhaps whenever a window using a menu is selected, the menu is kept on top? Has anyone got a more recent edition of the Open Look Functional Specification than this Review Draft from July 15?