create new tag
view all tags

Known Issues

Table Widget Editor

  • Some planned features are not yet implemented:
    • There is no spec to enable/disable multi-select
    • There is no option to require that at least one record be selected by the user at runtime.
    • There is no way to specify a child constraint for a table source process. This means that all of the records in the PCF must be read each time the table is populated unless you use a temporary file that you manually populate.
    • There is no ability to specify GUI options for column fields.
    • There should be an event point for Pre-Display
    • There should be an option intercept event point with the ability to intercept table events such as click, double-click, etc.
    • There is no option to specify which column the table should be sorted on when initially displayed. Records are presented in Primary key order.
    • There is no option to define column headings and their GUI attributes. Column heading text is taken from the data dictionary definition of the field.
    • There is no option to specify that a field (column) should perform a data lookup. Consequently, ILF code must be used in the Post PCF Read event point to manually retrieve data.

Table Widget Runtime

  • Performance may be an issue if you are loading a large number of records, depending on network speed, server load, amount of data and desktop processor. For example, loading 10,000 records from DMO CONTACT takes 2-3 seconds. Reading all 10,000 records to find the contacts for a selected Prospect is less than a second (using --- INCLUDE RECORD in Post PCF Read of the Table Resource).
  • Appx navigation keys take priority when in the Table Widget. Any key that would set --- OPTION (eg, Page Up/Page Down) will be returned to your input process and will not affect the table widget. Other keys, such as cursor up/down, can be used to navigate in the Table Widget.
  • Date columns sort based on the displayed value, not the actual date. For example, dates displayed as mm/dd/yy will not sort in date order.
  • At runtime, you cannot click on a row to select it unless all modifiable fields on the screen have satisfied the hard edits which are enforced by the engine. For example, an invalid character in a numeric field on the same screen will prevent you from selecting a record.

Drag & Drop Runtime

  • It is the designers responsibility to manage the files dropped in dropCachePath, the client will not delete them for you.
  • On the Mac, the client does not get the focus after a drop action.

Better HTML Widget

  • HTML Editor is not able to load a resource which references a CKEditor Config file. The resource must reference a file which is in the format of a compiled CKEditor Config file and must conform to the format of a compiled config file.
  • There are problems if you attempt to use the HTML Editor widget on "small" text fields.
    • If the field has three rows or less, the toolbar of the editor will completely overlay the field making it impossible to edit the field.
    • If the field has fewer than 22 rows, you will not be able to use the Spellchecker option because the dialog that pops up is clipped at the top and bottom rendering it unusable.
    • If the field has fewer than 13 rows, you will not be able to use the Find or the Find and Replace options because the dialog that pops up is clipped at the top and bottom rendering it unusable.
    • The link dialog also get clipped. I haven't tried the table dialog but I suspect that it also gets clipped.
  • When the editor window has the focus, none of the APPX keys work. END, CANCEL, OPTION, TAB, etc. don't work. The toolbar buttons do still work so you can click on ENTER and CANCEL. To get out of the editor field you must use the mouse to click on the next field. END, CANCEL, TAB, OPTION, and perhaps some of the other APPX keys need to be honored even when editing text. TAB has no meaning within HTML except when used within a <pre> tag so I definitely would like to see TAB be available to TAB out of the editor field to the next field.

Option Numbers in Design Mode

  • Option numbers are now displayed on buttons on the image editor if Show Option Numbers is turned on. But, there is no toolbar button or pulldown menu option to turn it on or off. It must be turned on or off by using the right-click menu. Better than nothing but not obvious.


Read what other users have said about this page or add your own comments.

-- JeanNeron - 2012-06-14

Edit | Attach | Watch | Print version | History: r62 < r61 < r60 < r59 < r58 | Backlinks | Raw View | Raw edit | More topic actions
Topic revision: r62 - 2013-02-04 - JeanNeron
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback