Claw 1.2 bug list

1. (Builder) If a window is created (via New Window) while in simulation mode, a walkback (rather than the window) appears. No data is lost, the project still can be saved.
2. (Builder) If a menu item is activates a dialog box, and the dialog box is deleted, a later attempt to edit the menu item will produce a walkback.
3. (Builder) When a project is loaded by double-clicking in Explorer (or by giving its name on the command line), a walkback message appears. The error can be ignored; it is self-correcting. Or the problem can be avoided completely by loading projects with "Open".
4. (Builder) When a radio button set having the default "Claw generates" identifier is simulated, clicking some of the buttons may cause the window to vanish or other erratic behavior.
5. (Builder) The case of radio button labels is improperly simulated, so that the labels may appear differently in the generated program.
6. If a Claw listbox (any type derived from Claw.Listbox.Root_Listbox_Type) is destroyed and recreated using the same object, the second Create will raise Claw.Not_Valid_Error for no reason.
7. Claw.Bitmaps.IO cannot read some 24-bit color bitmaps. This also affects the builder: problem bitmaps will not display in the sample box or in graphics.
8. Claw.Tooltips.Set_Durations uses the wrong word to set the timeouts. The result is that all of the timeouts are set to zero, not matter what the arguments are.
9. For a basic listbox, setting the key value when using Add_Text, Add_Text_to_End, and Insert_Text does not work. (It does work for a drop-down listbox and for comboboxes). To workaround the problem, use Add_Key to set the key value for basic listboxes.
10. (Builder) For an integer edit control with a subtype (rather than a type), if the initial value is negative, the generated code will not compile.
11. (Builder) Sometimes, after editing a menu item label, any access key is rejected as not being in the label. Workaround: set the access key to blank; then edit the label again and key in the entire label; finally, set the access key appropriately.
12. (Builder) If more than 20 top-level windows are created, the Builder crashes.
13. (Builder) If a child control of a group box uses a font (other than that of the group box), the font object may not be generated.
14. (Builder) If a radio button set is used in the application window, the selected value is never read and stored into the value component. Work around the problem by calling the Get_Selection in the appropriate instantiation to get the value before using it.
15. (Builder) A default sized radio button set is displayed differently (shorter with the buttons closer together) than it is the compiled, generated code. This problem can be worked around by simply using a fixed size radio button set: clear the "Use Default Size" box on the location page.
16. Claw.Radio_Button_Set.Move incorrectly calculates the size of a default sized set, using a size that is too small (but still readable). This means that the size calculated by Move is different than the size calculated by Create.
17. Calling Claw.Tooltip.Add_Tooltip for a rectangle without an Id or with a Claw-generated Id don't show a tooltip. Work around the problem by calling the Claw.Tooltip.Add_Tooltip with the Id parameter.
18. If the file list returning version of Open_File is called without the Explorer_Format flag, Windows always uses an old style dialog. However, Claw sometimes thinks that a new-style dialog was used, and thus fails to parse the returned list properly. Work around the problem by always specifying the Explorer_Format flag or by setting Autoposition to True.
19. (Builder) If the last item (or submenu) in a menu is deleted (leaving an empty menu), CBuild may crash or pop up error messages.
20. (Builder) If a project contains more than one menu, the builder may assign the same Id number to more than one menu item. (This will only happen when the second or later menus are initially created.) That means that only one of the actions will be executed when the program is generated and run; both items will execute that action. If you suspect this is happening, use the Identifier page to check the values of the menu identifier. (It is the number at the bottom; it may be displayed in grey, but it will display the number being used.) If there is a problem, manually correct it by clearing "Best way" and selecting "Manual Identifier Selection".
21. (Builder) If a menu does not contain an exit command (that is, a command with the standard action Exit), or the exit command is moved to a new command, the builder may generate code that either does not exit properly, or raises an exception when run. (In the latter case, the program will never appear when started.) The problem can be worked around by always having an exit command in your menus (a good idea anyway), and showing the application window just before generating code.
22. (Builder) The Builder allows entering a reserved word into an box that requires an Ada identifier, but the generated code will not compile.
23. (Builder) Integer and Float edit controls reset justification to Default when the project is loaded from a file, if the target OS is not Windows 98/2000 and (for Integer edit controls) the up-down arrow is off. Work around the problem by using Default justification, which is right justification for these targets (but see the next bug).
24. (Builder) Integer and Float edit controls use the wrong justification in the generated code for Default justification. The resulting program does not match the simulated program. Work around the problem by specifying Right justification (but see the previous bug).
25. (Builder) If the application window is cut or deleted, and the project properties is opened (main page), an application error will appear.
26. (Builder) RC cannot compile a menu with empty submenus. Either avoid empty submenus, or set "Use Claw code whenever possible" in the project properties (in which case the menus will not be defined in the resource file).
27. If an modal dialog object is reused, and it contains a radio button set component, Already_Valid_Error is raised incorrectly. Is_Valid would return False for the set component. Work around the problem by avoiding reuse of the object, or by explicitly Destroying the radio button set component.
28. (Builder) If the default menu is used, and a custom exit handler is used, the application cannot be exited. Work around the problem by explicitly defining a menu for the application.
29. (Builder) Edit controls may lose their initial values. This occurs if the control is used in other than a dialog box, or if validation handlers are used for other controls in the dialog. The control will always be filled with blanks, no matter what value is specified.
    For string edit controls, the problem can be worked around by specifying a control size, rather than letting Claw select a size. No workaround is available for numeric edit controls.
30. (Builder) The (specified, non-default) location of a dialog box is relative to the parent. The documentation implies that it is relative to the screen. (The documentation is incorrect.)
31. The Boolean function Claw.Tree_View.Is_Root_Item returns the wrong answer in all cases.
32. The function Claw.Window_Operations.Get_Desktop leaves a "lost" window behind after it is called; this window may raise an exception, hang the program, or do something else bad (depending on the compiler used) when the program exits.
33. If a DLL_Object is reused (that is Load is called after a previous Free), Already_Valid_Error will be raised for no reason.
34. Claw.Rectangles.Subtract and "-" always return an empty rectangle.