DOCSLIB.ORG

Menu Manager Reference

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Menu Manager Reference Menu Manager Reference February 26, 2004 Even though Apple has reviewed this manual, APPLE MAKES NO WARRANTY OR Apple Computer, Inc. REPRESENTATION, EITHER EXPRESS OR © 1992, 2004 Apple Computer, Inc. IMPLIED, WITH RESPECT TO THIS MANUAL, ITS QUALITY, ACCURACY, All rights reserved. MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. AS A RESULT, THIS MANUAL IS SOLD ªAS IS,º AND YOU, THE No part of this publication may be PURCHASER, ARE ASSUMING THE ENTIRE reproduced, stored in a retrieval system, or RISK AS TO ITS QUALITY AND ACCURACY. transmitted, in any form or by any means, IN NO EVENT WILL APPLE BE LIABLE FOR mechanical, electronic, photocopying, DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES recording, or otherwise, without prior RESULTING FROM ANY DEFECT OR written permission of Apple Computer, Inc., INACCURACY IN THIS MANUAL, even if with the following exceptions: Any person advised of the possibility of such damages. is hereby authorized to store documentation THE WARRANTY AND REMEDIES SET FORTH ABOVE ARE EXCLUSIVE AND IN on a single computer for personal use only LIEU OF ALL OTHERS, ORAL OR WRITTEN, and to print copies of documentation for EXPRESS OR IMPLIED. No Apple dealer, agent, or employee is authorized to make any personal use provided that the modification, extension, or addition to this documentation contains Apple’s copyright warranty. notice. Some states do not allow the exclusion or limitation of implied warranties or liability for The Apple logo is a trademark of Apple incidental or consequential damages, so the Computer, Inc. above limitation or exclusion may not apply to you. This warranty gives you specific legal Use of the “keyboard” Apple logo rights, and you may also have other rights which vary from state to state. (Option-Shift-K) for commercial purposes without the prior written consent of Apple may constitute trademark infringement and unfair competition in violation of federal and state laws. No licenses, express or implied, are granted with respect to any of the technology described in this document. Apple retains all intellectual property rights associated with the technology described in this document. This document is intended to assist application developers to develop applications only for Apple-labeled or Apple-licensed computers. Every effort has been made to ensure that the information in this document is accurate. Apple is not responsible for typographical errors. Apple Computer, Inc. 1 Infinite Loop Cupertino, CA 95014 408-996-1010 Apple, the Apple logo, Aqua, Carbon, Mac, Mac OS, MacApp, Macintosh, and QuickDraw are trademarks of Apple Computer, Inc., registered in the United States and other countries. PowerPC and and the PowerPC logo are trademarks of International Business Machines Corporation, used under license therefrom. Simultaneously published in the United States and Canada. Contents Chapter 1 Menu Manager Reference 7 Menu Manager Functions 7 Creating and Disposing of Menus 8 Manipulating the Root Menu 14 Manipulating the Menu Bar 16 Adding and Removing Menus 21 Manipulating and Accessing Menu Characteristics 24 Drawing Menus and Menu Items 34 Adding and Deleting Menu Items 39 Associating Data With Menu Items 41 Enabling Menus and Menu Items 51 Manipulating Menu Item Text 59 Manipulating and Accessing Menu Item Characteristics 68 Responding to Menu Events and User Selections 89 Handling Contextual Menu Plugins 98 Deprecated Functions 100 Menu Manager Callback 129 MenuDefProcPtr 129 Menu Manager Data Types 135 HMenuBarHeader 135 HMenuBarMenu 136 MCEntry 136 MDEFDrawData 140 MDEFDrawItemsData 140 MDEFFindItemData 141 MDEFHiliteItemData 141 MenuBarHandle 142 MenuBarHeader 142 MenuBarMenu 143 MenuCommand 143 MenuCRsrc 143 MenuDefSpec 143 MenuDefUPP 144 MenuHandle 144 MenuID 144 MenuItemDataRec 145 MenuItemID 147 3 © 1992, 2004 Apple Computer, Inc. All Rights Reserved. CONTENTS MenuItemIndex 147 MenuRef 147 MenuTrackingData 147 Menu Manager Constants 148 Menu Manager Result Codes 171 Appendix A Unsupported Functions 173 Document Revision History 175 Index 177 4 © 1992, 2004 Apple Computer, Inc. All Rights Reserved. Tables Chapter 1 Menu Manager Reference 7 Table 1-1 Metacharacters available to pass in AppendMenu 101 Appendix A Unsupported Functions 173 Table A-1 Porting notes for unsupported Menu Manager functions 174 Document Revision History 175 Table RH-1 Document revision history 175 5 © 1992, 2004 Apple Computer, Inc. All Rights Reserved. TABLES 6 © 1992, 2004 Apple Computer, Inc. All Rights Reserved. CHAPTER 1 Menu Manager Reference Framework: Carbon/Carbon.h Header: Menus.h You can use the Menu Manager to create and manage the menus in your application. Menus allow the user to view or choose from a list of choices and commands that your application provides. All Mac OS applications should provide these standard menus: the Application menu, the File menu, and the Edit menu. Carbon supports the Menu Manager, with the following changes: ■ Your application must use the functions defined by the Menu Manager whenever it creates and disposes of Menu Manager data structures. Some applications, for example, create menus by using the Resource Manager function GetResource (instead of the Menu Manager function GetMenu) and dispose of them by calling ReleaseResource instead of DisposeMenu. This practice is not supported in Carbon. ■ The MenuInfo structure is opaque in Carbon. You must revise your application so that it accesses Menu Manager data structures only through accessor functions. ■ Menu color information tables are not recommended in Carbon. ■ You are strongly encouraged to adopt the standard Mac OS menu definition functions (also known as MDEFs) in your application. Your menus will then inherit the systemwide appearance and, furthermore, take advantage of other Menu Manager enhancements planned for the future. Note, however, that if you must use custom menu definition procedures, you must compile them as PowerPC-native code. If you are deploying applications for Mac OS X v10.3 and later, you should create your custom menu definitions by creating HIView menu subclasses. Menu Manager Functions Function descriptions are grouped by the tasks for which you use the functions. For an alphabetical list of functions, go to the API index at the end of the document. Menu Manager Functions 7 © 1992, 2004 Apple Computer, Inc. All Rights Reserved. CHAPTER 1 Menu Manager Reference Creating and Disposing of Menus CreateNewMenu Creates a new, untitled, empty menu. OSStatus CreateNewMenu ( MenuID inMenuID, MenuAttributes inMenuAttributes, MenuRef * outMenuRef ); Parameter Descriptions inMenuID The menu ID to use for the new menu. Note that zero is a valid ID in Carbon. inMenuAttributes The menu attributes to use for the new menu. See ªMenu Item Attribute Constantsº (page 154) for a list of possible values. outMenuRef On exit, contains the new menu. function result A result code. See ªMenu Manager Result Codesº (page 171). Discussion Unless you need to create new menus on-the-fly, you should not use functions like CreateNewMenu that create menus programmatically. Instead, you should define menus in Interface Builder, store them as nib files, and then call the Interface Builder Services function CreateMenuFromNib to create them. CreateNewMenu is preferred over NewMenu because it allows you to specify the menu©s attributes and it does not require you to specify a Str255-based menu title. To set the menu title, you should use SetMenuTitleWithCFString (page 25). Availability Available in CarbonLib 1.0 and later. Available in Mac OS X v10.0 and later. Header: Menus.h DuplicateMenu Creates a new menu that is a copy of another menu. OSStatus DuplicateMenu ( MenuRef inSourceMenu, MenuRef * outMenu ); Parameter Descriptions inSourceMenu The menu to duplicate. 8 Menu Manager Functions © 1992, 2004 Apple Computer, Inc. All Rights Reserved. CHAPTER 1 Menu Manager Reference outMenu On exit, a copy of the source menu. function result A result code. See ªMenu Manager Result Codesº (page 171). Discussion Unlike RetainMenu (page 9), DuplicateMenu creates an entirely new menu that is an exact copy of the original menu. The menu definition for the new menu will receive an initialization message/event after the menu has been fully created. Availability Available in CarbonLib 1.1 and later. Available in Mac OS X v10.0 and later. Header: Menus.h RetainMenu Increments the reference count of a menu. OSStatus RetainMenu ( MenuRef inMenu ); Parameter Descriptions inMenu The menu whose reference count you want to increment. function result A result code. See ªMenu Manager Result Codesº (page 171). Discussion RetainMenu does not create a new menu. It simply adds one to the reference count. Version Notes In Mac OS X v10.2 and later, all menus are Core Foundation CFTypes, so you can optionally call CFRetain instead of RetainMenu. Availability Available in CarbonLib 1.1 and later. Available in Mac OS X v10.0 and later. Header: Menus.h ReleaseMenu Decrements the retain count of a menu. OSStatus ReleaseMenu ( MenuRef inMenu ); Menu Manager Functions 9 © 1992, 2004 Apple Computer, Inc. All Rights Reserved. CHAPTER 1 Menu Manager Reference Parameter Descriptions inMenu The menu whose retain count to decrement. If the retain count falls to zero, the menu is destroyed. function result A result code. See ªMenu Manager Result Codesº (page 171). Discussion The reference that you pass in the theMenu parameter is not valid after DisposeMenu returns. This function is identical to DisposeMenu (page 10). Version Notes In Mac OS X v10.2 and later, all menus are Core Foundation CFTypes, so you can optionally call CFRelease instead of ReleaseMenu. Availability Available in CarbonLib 1.1 and later. Available in Mac OS X v10.0 and later. Header: Menus.h DisposeMenu Decrements the retain count of a menu. void DisposeMenu ( MenuRef theMenu ); Parameter Descriptions theMenu The menu whose retain count to decrement. If the retain count falls to zero, the menu is destroyed. Discussion The reference that you pass in the theMenu parameter is not valid after DisposeMenu returns. This function is identical to ReleaseMenu (page 9). Availability Available in CarbonLib 1.0 and later when running Mac OS 8.1 or later.
Load more

Recommended publications
  • Adopting the Aqua Interface
    INSIDE MAC OS X Adopting the Aqua Interface Updated for Mac OS X Public Beta Release. 9/8/00 © Apple Computer, Inc. 2000 Apple Computer, Inc. Even though Apple has reviewed this © 2000 Apple Computer, Inc. manual, APPLE MAKES NO All rights reserved. WARRANTY OR REPRESENTATION, EITHER EXPRESS OR IMPLIED, WITH No part of this publication may be RESPECT TO THIS MANUAL, ITS reproduced, stored in a retrieval QUALITY, ACCURACY, system, or transmitted, in any form or MERCHANTABILITY, OR FITNESS by any means, mechanical, electronic, FOR A PARTICULAR PURPOSE. AS A photocopying, recording, or RESULT, THIS MANUAL IS SOLD “AS otherwise, without prior written IS,” AND YOU, THE PURCHASER, ARE permission of Apple Computer, Inc., ASSUMING THE ENTIRE RISK AS TO with the following exceptions: Any ITS QUALITY AND ACCURACY. person is hereby authorized to store documentation on a single computer IN NO EVENT WILL APPLE BE LIABLE for personal use only and to print FOR DIRECT, INDIRECT, SPECIAL, copies of documentation for personal INCIDENTAL, OR CONSEQUENTIAL use provided that the documentation DAMAGES RESULTING FROM ANY contains Apple’s copyright notice. DEFECT OR INACCURACY IN THIS The Apple logo is a trademark of MANUAL, even if advised of the Apple Computer, Inc. possibility of such damages. Use of the “keyboard” Apple logo THE WARRANTY AND REMEDIES SET (Option-Shift-K) for commercial FORTH ABOVE ARE EXCLUSIVE AND purposes without the prior written IN LIEU OF ALL OTHERS, ORAL OR consent of Apple may constitute WRITTEN, EXPRESS OR IMPLIED. No trademark infringement and unfair Apple dealer, agent, or employee is competition in violation of federal authorized to make any modification, and state laws.
    [Show full text]
  • SYSTEM SOFTWARE, MEMORY, and RESOURCES Includes Demonstration Program Sysmemres
    1 SYSTEM SOFTWARE, MEMORY, AND RESOURCES Includes Demonstration Program SysMemRes Macintosh System Software All Macintosh applications make many calls, for many purposes, to Macintosh system software functions. Such purposes include, for example, the creation of standard user interface elements such as windows and menus, the drawing of text and graphics, and the coordination of the application's actions with other open applications.1 The majority of system software functions are components of either the Macintosh Toolbox or the Macintosh Operating System. In essence: • Toolbox functions have to do with mediating your application with the user. They relate, in general, to the management of elements of the user interface. • Operating System functions have to do with mediating your application with the Macintosh hardware, performing such basic low-level tasks as file input and output, memory management and process and device control. Managers The entire collection of system software functions is further divided into functional groups which are usually known as managers.2 Toolbox The main Toolbox managers are as follows: QUICKDRAW WINDOW MANAGER DIALOG MANAGER CONTROL MANAGER MENU MANAGER TEXTEDIT EVENT MANAGER RESOURCE HELP MANAGER SCRAP MANAGER FINDER INTERFACE LIST MANAGER MANAGER SOUND MANAGER SOUND INPUT STANDARD FILE NAVIGATION APPEARANCE FOLDER MANAGER PACKAGE SERVICES MANAGER MANAGER Introduced with Mac OS 8.0. Note that Navigation Services renders Standard File Package obsolescent 1 The main other open application that an application needs to work with is the Finder, which is responsible for keeping track of files and managing the user’s desktop. The Finder is not really part of the system software, although it is sometimes difficult to tell where the Finder ends and the system software begins.
    [Show full text]
  • Volume 2, Number 9 September 23, 1996 [email protected] Cover
    About This Particular Macintosh™ 2.09: About the personal computing experience™ Volume 2, Number 9 September 23, 1996 Send requests for FREE subscriptions to: [email protected] Cover Art “OpenDoc” © 1996 Kevin Work: [email protected] http://www.shsu.edu/~stdklw03/ We need new cover art every month! Write to us! Contributors H.M. Fog Robert Paul Leitao Robert Madill Michael Tsai Macintosh users like you Please write for ATPM! Check out the Guidelines Staff Editor - Michael Tsai Managing Editor - Robert Paul Leitao Opinionated Associate Editor - Mike Shields Cover Story Editor - Vacant Associate Editor For Reviews - Michael Tsai Shareware Reviews Editor - Vacant Subscription Manager - Robert Paul Leitao Human Spell Checker - Belinda Wagner Webzinger - Evan Trent Beta Testers - The Staff In Charge of Design - Michael Tsai Typewriter Style Section Headers - RD Novo Blue Apple Icon Designs - Marc Robinson The Tools BBEdit 4.0.1 ClarisWorks 4.0v4 DOCMaker 4.6.1 Emailer 1.1v2 Illustrator 6 Kai’s PowerTools 3.1 Photoshop 3.0.5 SpellCatcher 1.5.6 The Fonts Cheltenham Cloister Garamond Geneva Gill Sans Helvetica Isla Bella Where to Find ATPM Online and downloadable issues are available at the new ATPM Web Page: http://www.museproductions.com/ATPM America Online : search “atpm” Italica BBS, La Coruna, Spain North Coast BBS NYMUG, New York City SenseNet, New York City Tulsa Info Mall BBS, Oklahoma Raven Net, British Columbia SpiderNet, Holland Speaker's Corner BBS, Jacksonville Info-Mac and all its Mirrors Any others? Let us know! © 1995-96, All Rights Reserved (Exceptions noted below) Reprints Articles and original art cannot be reproduced without the express permission of ATPM, unless otherwise noted.
    [Show full text]
  • Mac OS 8 Revealed
    •••••••••••••••••••••••••••••••••••••••••••• Mac OS 8 Revealed Tony Francis Addison-Wesley Developers Press Reading, Massachusetts • Menlo Park, California • New York Don Mills, Ontario • Harlow, England • Amsterdam Bonn • Sydney • Singapore • Tokyo • Madrid • San Juan Seoul • Milan • Mexico City • Taipei Apple, AppleScript, AppleTalk, Color LaserWriter, ColorSync, FireWire, LocalTalk, Macintosh, Mac, MacTCP, OpenDoc, Performa, PowerBook, PowerTalk, QuickTime, TrueType, and World- Script are trademarks of Apple Computer, Inc., registered in the United States and other countries. Apple Press, the Apple Press Signature, AOCE, Balloon Help, Cyberdog, Finder, Power Mac, and QuickDraw are trademarks of Apple Computer, Inc. Adobe™, Acrobat™, and PostScript™ are trademarks of Adobe Systems Incorporated or its sub- sidiaries and may be registered in certain jurisdictions. AIX® is a registered trademark of IBM Corp. and is being used under license. NuBus™ is a trademark of Texas Instruments. PowerPC™ is a trademark of International Business Machines Corporation, used under license therefrom. SOM, SOMobjects, and System Object Model are licensed trademarks of IBM Corporation. UNIX® is a registered trademark of Novell, Inc. in the United States and other countries, licensed exclusively through X/Open Company, Ltd. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this book, and Addison-Wesley was aware of a trademark claim, the designations have been printed in initial capital letters or all capital letters. The author and publisher have taken care in the preparation of this book, but make no express or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for incidental or consequential damages in connection with or arising out of the use of the information or programs contained herein.
    [Show full text]
  • Develop-22 9506 June 1995.Pdf
    develop E D I T O R I A L S T A F F T H I N G S T O K N O W C O N T A C T I N G U S Editor-in-Cheek Caroline Rose develop, The Apple Technical Feedback. Send editorial suggestions Managing Editor Toni Moccia Journal, a quarterly publication of or comments to Caroline Rose at Technical Buckstopper Dave Johnson Apple Computer’s Developer Press AppleLink CROSE, Internet group, is published in March, June, [email protected], or fax Bookmark CD Leader Alex Dosher September, and December. develop (408)974-6395. Send technical Able Assistant Meredith Best articles and code have been reviewed questions about develop to Dave Our Boss Greg Joswiak for robustness by Apple engineers. Johnson at AppleLink JOHNSON.DK, His Boss Dennis Matthews Internet [email protected], CompuServe This issue’s CD. Subscription issues Review Board Pete “Luke” Alexander, Dave 75300,715, or fax (408)974-6395. Or of develop are accompanied by the Radcliffe, Jim Reekes, Bryan K. “Beaker” write to Caroline or Dave at Apple develop Bookmark CD. This CD contains Ressler, Larry Rosenstein, Andy Shebanow, Computer, Inc., 1 Infinite Loop, M/S a subset of the materials on the monthly Gregg Williams 303-4DP, Cupertino, CA 95014. Developer CD Series, available from Contributing Editors Lorraine Anderson, APDA. Included on the CD are this Article submissions. Ask for our Steve Chernicoff, Toni Haskell, Jody Larson, issue and all back issues of develop along Author’s Guidelines and a submission Cheryl Potter with the code that the articles describe.
    [Show full text]
  • About This Particular Macintosh 6.03
    Cover ATPM About This Particular Macintosh™ 6.03: About the personal computing experience™ Volume 6, Number 3 March 1, 2000 Sign up for free subscriptions at: http://www.atpm.com/subscribe or send email to: [email protected] ATPM 6.03 ←→1 Cover Cover Art Copyright © 2000 David Knopfler david@knopfler.com http://www.knopfler.com We need new cover art every month! Write to us! Contributors Eric Blair Daniel Chvatik Paul Fatula Scott Feldstein Matthew Glidden Edward Goss Lisa Haller Tom Iov ino Nick Kratz Robert Paul Leitao William Lovett Colin Mansfield Jamie McCornack Grant Osborne David Ozab David Spencer Michael Tsai Christopher Turner Macintosh users like you Please write for ATPM! Check out the FAQ. Editorial Staff Publisher/Editor-in-Chief - Michael Tsai Managing Editor - Daniel Chvatik Associate Editor/Reviews - Paul Fatula ATPM 6.03 ←→2 Cover Associate Editor/Shareware Reviews - William Lovett Copy Editors - Raena Armitage Johann Campbell Paul Fatula Brooke Smith Adam Zaner Publicity Manager - Christopher Turner Contributing Editor/Welcome - Robert Paul Leitao Contributing Editors/Opinion - Tom Iovino Scott Feldstein Contributing Editors/Reviews - Eric Blair Evan Trent Vac a nt Contributing Editor/How To’s & Reviews - Jamie McCornack Contributing Editor/Trivia - Edward Goss Contibuting Editor/Music - David Ozab Contributing Editor/Networking - Matthew Glidden Contributing Editor/Web - David Spencer Help Jedi - Christopher Turner Hollywood Guy - Mike Shields Webmaster - Michael Tsai Assistant Webmaster - A. Lee Bennett Interviews
    [Show full text]
  • SYSTEM SOFTWARE, POWERPC RUN-TIME ENVIRONMENT, MANAGING MEMORY, and RESOURCES Demonstration Program: Sysmemres
    1 SYSTEM SOFTWARE, POWERPC RUN-TIME ENVIRONMENT, MANAGING MEMORY, AND RESOURCES Demonstration Program: SysMemRes System Software All Macintosh applications make many calls, for many purposes, to system software functions. Such purposes include, for example, the creation of standard user interface elements such as windows and menus, the drawing of text and graphics, and the coordination of the application's actions with other open applications.1 The entire collection of system software functions is divided into functional groups known as managers. In Carbon, each manager is part of a higher-level grouping called a manager group. The manager groups and their constituent managers are shown in the following, in which those managers of particular relevance to this book appear in bold typeface: Application Utilities Facilities for extending human interface features and data-sharing capabilities beyond those provided by the Human Interface Toolbox. AltiVec Utilities Find By Content Translation Manager Carbon Core Essential services that are generally devoid of a user interface, including memory and process management. Alias Manager Collection Manager Component Manager File Manager Folder Manager Low Memory Accessors Memory Management Utilities Memory Manager Mixed Mode Manager Multiprocessing Services Notification Manager Pascal String Utilities Resource Manager Thread Manager Time Manager Common OS Services Display Manager Gestalt Manager Power Manager Process Manager Speech Recognition Manager Speech Synthesis Manager Core Foundation Abstracts several operating system utitlities fundamental to both Mac OS 8/9 and Mac OS X. Base Services Bundle Services Collection Services Plug-in Services Preferences Services Property List Services String Services URL Services Utility Services XML Services Graphics Services Allows applications to construct and render images.
    [Show full text]
  • MBS FMAPI Plugin Documentation
    MBS FMAPI Plugin Documentation Christian Schmitz September 6, 2021 2 0.1 Introduction This is the PDF version of the documentation for the Xojo Plug-in from Monkeybread Software Germany. Plugin part: MBS FMAPI Plugin 0.2 Content • 1 List of all topics 3 • 2 List of all classes 7 • 3 All items in this plugin 9 • 4 List of Questions in the FAQ 49 • 5 The FAQ 59 Chapter 1 List of Topics • 3 Claris FileMaker Data API 9 – 3.1.1 class FMAdminMBS 9 ∗ 3.1.5 Constructor 10 ∗ 3.1.6 CreateBackupSchedule(schedule as Dictionary) as FMResponseMBS 10 ∗ 3.1.7 CreateFileMakerScriptSchedule(schedule as Dictionary) as FMResponseMBS 11 ∗ 3.1.8 CreateMessageSchedule(schedule as Dictionary) as FMResponseMBS 11 ∗ 3.1.9 CreateScriptSequenceSchedule(schedule as Dictionary) as FMResponseMBS 12 ∗ 3.1.10 CreateSystemScriptSchedule(schedule as Dictionary) as FMResponseMBS 12 ∗ 3.1.11 CreateVerifySchedule(schedule as Dictionary) as FMResponseMBS 12 ∗ 3.1.12 DeleteSchedule(scheduleID as Integer) as FMResponseMBS 13 ∗ 3.1.13 DisconnectClient(ClientID as Integer, messageText as String = ””, graceTime as Inte- ger = -1) as FMResponseMBS 13 ∗ 3.1.14 DuplicateSchedule(scheduleID as Integer) as FMResponseMBS 13 ∗ 3.1.15 EditSchedule(scheduleID as Integer, schedule as Dictionary) as FMResponseMBS 14 ∗ 3.1.16 GetDataAPISettings as FMResponseMBS 14 ∗ 3.1.17 GetPHPSettings as FMResponseMBS 15 ∗ 3.1.18 GetSchedule(scheduleID as Integer) as FMResponseMBS 15 ∗ 3.1.19 GetServerGeneralSettings as FMResponseMBS 15 ∗ 3.1.20 GetServerSecuritySetting as FMResponseMBS 15 ∗ 3.1.21 GetServerStatus as FMResponseMBS 15 ∗ 3.1.22 GetWebDirectSettings as FMResponseMBS 15 ∗ 3.1.23 GetWPESettings as FMResponseMBS 16 ∗ 3.1.24 GetWPESettings(MachineID as Integer) as FMResponseMBS 16 ∗ 3.1.25 GetXDBCSettings as FMResponseMBS 16 ∗ 3.1.26 GetXMLSettings as FMResponseMBS 16 ∗ 3.1.27 ListClients as FMResponseMBS 16 ∗ 3.1.28 ListDatabases as FMResponseMBS 16 3 4 CHAPTER 1.
    [Show full text]
  • Aqua Human Interface Guidelines
    CHAPTER 1 1 Introduction to the Aqua Human Interface Guidelines Mac OS X is the world’s most advanced operating system, combining a powerful core foundation with a new and compelling user interface called Aqua. With brilliant new features and an aesthetically refined use of color, transparency, and animation, Aqua makes computing even easier for new users, while providing the productivity that professional users have come to expect of the Macintosh. The user interface features, behaviors, and appearances introduced in Aqua deliver a well organized and cohesive user experience available to all applications developed for Mac OS X. This document, which covers features up to Mac OS X version 10.2, describes what you need to do to design your application for Aqua. Primarily intended for Carbon and Cocoa developers who want their applications to look right and behave correctly in Mac OS X, these guidelines provide examples of how to use Aqua interface elements. Java application developers will also find these guidelines useful. This document assumes that you are familiar with basic software design principles. Specific principles of designing for the Mac OS are summarized in the next chapter, “Human Interface Design Principles” (page 27). Important This document has been reviewed for technical accuracy, but the information herein is subject to change. To receive notification of updates to this document and others, you can sign up for Apple Developer Connection’s free Online Program and receive the weekly ADC News email newsletter. For more details about the Online Program, see http://developer.apple.com/membership/ index.html. 21 Apple Computer, Inc.
    [Show full text]
  • THE APPEARANCE MANAGER Includes Demonstration Program Appearance
    6 THE APPEARANCE MANAGER Includes Demonstration Program Appearance Introduction The Appearance Manager, which was first introduced with Mac OS 8.0, had implications for the Menu Manager, the Window Manager, the Control Manager, and the Dialog Manager. The relatively minor implications in respect of the Menu Manager and Window Manager were incorporated into Chapter 3 — Menus and Chapter 4 — Windows. The most profound impact of the Appearance Manager, however, has been in the area of user interface objects known as controls, which are addressed at Chapter 7 — Introduction to Controls and at Chapter 14 — More on Controls. Accordingly, as a preparation for what is to come, this chapter now formally introduces the Appearance Manager, a component of the system software which represents the most significant improvement in the Macintosh user experience since the introduction of System 7. The Era of Themes The Appearance Manager ushers in the era of themes. Essentially, a theme is an interface "look" that spans all elements of the user interface and ties them together with a certain graphic design. Themes are data-driven, that is, all the data that describes the theme interface is contained in a theme file. This makes it easy to change themes on the fly. Fig 1 shows three windows, each in a separate theme. If one of these themes has been selected by the user, all elements of the user interface (menus, windows, controls, etc.) will appear in that theme. HIGH TECH GIZMO PLATINUM FIG 1 - WINDOWS IN THREE THEMES The Appearance Manager 6-1 At the time of writing, Platinum was the only available theme; however, switchable themes are very much part of the future of the Mac OS.
    [Show full text]
  • Human Interface Guidelines for Mac OS 8
    Human Interface Guidelines for Mac OS 8 WWDC Release May 1996 © Apple Computer, Inc. 1994 - 1996 Apple Computer, Inc. Linotype-Hell AG and/or its © 1994-1996 Apple Computer, Inc. subsidiaries. All rights reserved. ITC Zapf Dingbats is a registered No part of this publication may be trademark of International Typeface reproduced, stored in a retrieval Corporation. system, or transmitted, in any form QuickView™ is licensed from Altura or by any means, mechanical, Software, Inc. electronic, photocopying, recording, Simultaneously published in the or otherwise, without prior written United States and Canada. permission of Apple Computer, Inc., except to make a backup copy of any documentation provided on Even though Apple has reviewed this CD-ROM. manual, APPLE MAKES NO The Apple logo is a trademark of WARRANTY OR REPRESENTATION, Apple Computer, Inc. EITHER EXPRESS OR IMPLIED, WITH Use of the “keyboard” Apple logo RESPECT TO THIS MANUAL, ITS (Option-Shift-K) for commercial QUALITY, ACCURACY, purposes without the prior written MERCHANTABILITY, OR FITNESS consent of Apple may constitute FOR A PARTICULAR PURPOSE. AS A trademark infringement and unfair RESULT, THIS MANUAL IS SOLD “AS competition in violation of federal IS,” AND YOU, THE PURCHASER, and state laws. ARE ASSUMING THE ENTIRE RISK No licenses, express or implied, are AS TO ITS QUALITY AND granted with respect to any of the ACCURACY. technology described in this book. IN NO EVENT WILL APPLE BE Apple retains all intellectual LIABLE FOR DIRECT, INDIRECT, property rights associated with the SPECIAL, INCIDENTAL, OR technology described in this book. CONSEQUENTIAL DAMAGES This book is intended to assist RESULTING FROM ANY DEFECT OR application developers to develop INACCURACY IN THIS MANUAL, applications only for Apple-labeled even if advised of the possibility of such or Apple-licensed computers.
    [Show full text]
  • IGOR XOP 6 Toolkit Reference Manual
    IGOR XOP TOOLKIT REFERENCE MANUAL Version 6.40 WaveMetrics, Inc. Copyright This manual and the Igor XOP Toolkit are copyrighted by WaveMetrics with all rights reserved. Under copyright laws it is illegal for you to copy this manual or the software without written permission from WaveMetrics. WaveMetrics gives you permission to make unlimited copies of the software on any number of machines but only for your own personal use. You may not copy the software for any other reason. You must ensure that only one copy of the software is in use at any given time. Notice All brand and product names are trademarks or registered trademarks of their respective companies. Manual Revision: October 27, 2015 (6.40) © Copyright 2015 WaveMetrics, Inc. All rights reserved. WaveMetrics, Inc. PO Box 2088 Lake Oswego, OR 97035 USA Voice: 503-620-3001 FAX: 503-620-6754 Email: [email protected], [email protected] Web: http://www.wavemetrics.com/ Table of Contents Chapter 1 - Introduction to XOPs About This Manual .............................................................................................. 1 What is an XOP?.................................................................................................. 2 Who Can Write an XOP?..................................................................................... 2 A Brief History of Igor ........................................................................................ 2 XOP Toolkit 6.4..................................................................................................
    [Show full text]