![]() Void MyWindow::undoPushCallback( Widget, XtPointer clientData, XtPointer) Void MyWindow::pushCallback( Widget, XtPointer clientData, XtPointer)Ĭout add("Push", &MyWindow::undoPushCallback, (XtPointer) clientData) Void MyWindow::quitCallback ( Widget, XtPointer clientData, XtPointer ) Void MyWindow::undoThreeCallback( Widget, XtPointer clientData, XtPointer) Void MyWindow::undoTwoCallback( Widget, XtPointer clientData, XtPointer) Void MyWindow::undoOneCallback( Widget, XtPointer clientData, XtPointer) Void MyWindow::threeCallback( Widget, XtPointer clientData, XtPointer) Void MyWindow::twoCallback( Widget, XtPointer clientData, XtPointer) Static void undoCutCallback(Widget, XtPointer, XtPointer) ![]() Static void cutCallback(Widget, XtPointer, XtPointer) The undo callback function should reverse the effects of the item's action.įor example, the following static description describes a Cut menu item that executes the callback function cutCallback() when the user chooses the item and undoCutCallback() when the user undoes the command: To add undo support for an undoable menu item ( VkMenuAction and VkMenuToggle items), simply provide an undo callback function when you define the menu item. Providing Undo Support for Actions That Are Menu Items In most cases, all you need to provide for each command is a callback function that reverses the effects of that command. The undo manager also supports undoing command classes as implemented by the VkAction(3x) and VkMenuActionObject(3x) classes described in “Command Classes”. You can use the undo manager to support undoing any command, regardless of whether the user issues the command through a menu or through other interface methods (for example, pushbuttons). If you choose, you can also force the undo manager to provide only single-level undo support, where it remembers only the last command the user issued. Also, executing any non-undoable command clears the undo stack. Once a user has undone at least one command, executing any new command clears the undo stack. When the user undoes a command, the undo manager pops it from the stack, revealing the previously executed command. The undo manager keeps commands on a stack. To undo the command, the user simply chooses the undo manager's menu item.īy default, ViewKit's undo manager provides multi-level undo support. Whenever the user issues a command, the undo manager automatically updates the menu item to reflect the latest command. By default, the label of that menu item is “Undo: last_command”, where last_command is the name of the last command the user issued. The user interface to the ViewKit undo manager is a single menu item that you add to one of your application's menus. The ViewKit undo manager provides an easy-to-use method for users to undo commands that they issue to your application. Bulleted lists present alternate methods.The VkMenuUndoManager class is the basis of ViewKit's undo manager. Numbered lists present steps to perform in sequence. ![]() Lists The following two types of lists present procedures: 1. In text, Motif refers to C, C++, ViewKit, and UIL. The following icons indicate sections specific to particular languages: C UIL ViewKit C++ Java Note: Information that applies to all Motif environments does not use icons. The default directory is the following: /opt/bxpro-6.0 Most index entries are in lowercase: fonts fixed width 28 non-xlfd 228 Entries capitalized in Builder Xcessory are capitalized in the index: Force To Selected 161 Force to Selected Tree 161 Languages Because Builder Xcessory supports multiple programming languages, not all explanations or examples are applicable to all languages. 9 Browser Object Instance Hierarchy Browser Display Modes.10 Browser in Instances View Browser in Classes View Selecting Objects Panning the Browser File Menu.14 New (Ctrl+N).15 Open (Ctrl+O).16 Read (Ctrl+F) Save (Ctrl+S) Save As (Ctrl+A) Class.20 Import Generate refers to the directory into which the Builder Xcessory is installed. 3 Language Dialog.3 Builder Xcessory Main Windows. xi Notation Conventions.xii Definitions.xiv Prerequisite Knowledge.xvi Chapter 1 Introduction Overview. 54 Middlesex Turnpike, Bedford, MA Tel: Fax: Third printing January 2009ģ Contents How to Use This Manual Overview. No part of this book may be reproduced, transcribed, stored in a retrieval system, or transmitted in any form or by any means electronic, mechanical, photocopying, recording, or otherwise, without the prior written consent of Integrated Computer Solutions, Inc. The Builder Xcessory Reference Manual is copyrighted by Integrated Computer Solutions, Inc., with all rights reserved. 2 Copyright Integrated Computer Solutions, Inc.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |