1 
 2 09/21/87  menu_manager
 3 Known errors in the current release of menu_manager.
 4 #         Associated TR's
 5 Description
 6 
 7 18  phx18489
 8 menu_$create allows the creation of menus greater than the width
 9 specified in the menu_format.max_width element.  However it only
10 allocates enough space for a menu of max_width size.  This creates
11 problems when text outside of the allocated space is referenced.
12 
13 16
14 There is indeed a problem with the init documentation, interesting that
15 no one ever noticed it before.  There is no such thing as ft_menu_$init
16 or cb_menu_$init for that matter.
17 
18 The ft_menu_$init help in the info file actually goes to init2 (Same
19 for cb_menu_$init).  The manual ft_menu_$init1 and 2 sections of the
20 manual are correct but subtle.  init2 follows init1 and under init2 it
21 says THESE MUST BE THE FIRST CALLS.  It might be better if init1 and
22 init2 are listed together without the horizontal bar separating them.
23 
24 The cb_menu_$init1 section of the manual just leaves off init2.
25 However the rest of the section deals with init2 not init1.  init1 is
26 mentioned in the declarations section.
27 
28 The format of these two sections for ft_menu_ and cb_menu_ should be
29 the same since they are doing the same thing.
30 
31 14  phx15967
32 When using the menu system on SUPERBRAIN (and other terminals), the
33 screen does not clear on exit.  This problem seems to happen on
34 terminals without line insert/delete functionality.
35 
36 I have not been able to reproduce the problem.  I assume that a change
37 to the video system has fixed it.
38 
39 4
40 The command interface cannot get rid of the *'d menu choice except by
41 doing another menu_display, because the menu object with record of the *
42 is discarded.