Known Issues

Known Issues

Version 7.2.0

  1. When working on a large Eclipse RWT project, the workspace may become unresponsive. This can usually be fixed by restarting LiquidApps.
  2. If a header name is given to a Table Column, the name will not show up in the generated code.
  3. When using the Wireframe renderer, changes to some properties may appear not to take effect. These changes will be correctly reflected in the generated code.
  4. In a Task Model, auto sizing elements may not always work for very large objects or when many objects are selected.
  5. The Undo and Redo functions do not always work correctly.
  6. The LiquidApps workspace may become corrupted after deleting a User Interface or Logic Scripts component that is connected to other components. Be sure to remove all connection relationships between widgets before attempting a deletion.
  7. Lines connecting event handlers to their targets may disappear, or the event handler icon on a target may disappear from a target. The effects of the event handlers will still be retained, however.
  8. An event trigger icon may remain on a target widget after an event handler has been removed from it. The effects of the event handler should not occur, however.
  9. The wireframe render may unexpectedly be used to display a User Interface, especially when switching between Android and Swing User Interfaces.
  10. Copy and paste functionality may not work for buttons with icons attached to them.
  11. The zoom features may only work within the editor that was most recently opened.
  12. It may not be possible to delete an event handler which calls a script with an input once it has been attached to a widget and given an input source.
  13. Some projects created with very old versions of LiquidApps may not properly import into the latest version.
  14. Some widgets in RWT, such as radio buttons, may be rendered as if they were buttons.
  15. Enabling the Show Grid option may cause LiquidApps to perform sluggishly.
  16. Changing the target widgets for a previously created spacing guideline rule may not take effect.
  17. Changing the number of inputs in a Script that is connected to a Run Script activity may not take effect in the Run Script activity.
  18. Simulations of Scripts in which objects of different data types are compared may not execute as expected.
  19. The preview function for a Motif UI does not currently work.
  20. When performing a transformation between UI platforms, attached data (e.g. spreadsheets or images) may not be attached to the transformed copy.
  21. In the audit editor, previously fulfilled requirements may be marked as unfulfilled upon importing the project.
  22. Motif managers which hold only one primitive (e.g. Frame) shrink after deleting the primitive they contain.
  23. After generating a Requirements Document, newly added requirements may not appear on future Requirements Documents.