Number: 522 Date: 6-Apr-84 9':38':29 Submitter: le.pasa Source: CS.CHEE@UTEXAS-20.ARPA Subject: ADDMENU/DELETEMENU modifies menu for subsequent use Assigned To: Burton.pa Attn: Status: Closed In/By: Harmony Problem Type: Design - Impl Impact: Moderate Difficulty: Frequency: Priority: Hopefully System: Windows and Graphics Subsystem: Window System Machine: Disk: Lisp Version: Fugue.4 Source Files: Microcode Version: Memory Size: File Server: Server Software Version: Disposition: ' [Date': 6 Apr 84 11':56 PST' From': Burton.pa' Subject': ar# 522' fixed.]' ["Sannella.PA" "11-Sep-84 10':42':21" Description':]' ["Sannella.PA" "11-Sep-84 10':44':03" Disposition': Edit-Date':] Description: ' Mail-From': CS.CHEE created at 20-Mar-84 17':26':20' Date': Tue 20 Mar 84 17':26':20-CST' From': CS.CHEE@UTEXAS-20.ARPA' Subject': Menu problems.' To': 1100-SUPPORT@PARC-MAXC.ARPA' cc': CS.CHEE@UTEXAS-20.ARPA' ' ' Hi,' ' I''m having some problems manipulating menus, possibly' a bug in the ADDMENU and DELETEMENU function.' ' If one had a menu in which ITEMS is a list with a value' to be returned when selected field, ' ' eg. ITEMS <- ''((YES ''YES) (NO ''NO))' ' then if one added and deleted the menu,' ' eg. (PROGN (ADDMENU )' (DELETEMENU )' (MENU ))' will return a process number.' ' subsequent calls to the menu using (MENU ) would ' return some process number when an item of the menu is' selected, is this intentional or a bug? If it is' intentional, are there ways to preserve the meaning of' MENU so that it always returns the value to be returned' when selected?' ' -Chee-' Workaround: Test Case: Edit-By: Sannella.PA Edit-Date: 11-Sep-84 10':44':04