Known Issues

Table Widget Editor

• Check online help
• 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.
• There is no ability to specify GUI options for column fields.
• There should be separate event points for Post Read, Pre-Select, and 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.
• 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, there is no option to have a data lookup populate columns for fields from other files.

Table Resource Editor

• Check online help

Table Widget Runtime

• It seems that rewriting an ITEM (HTM VIEWER) to a table doesn’t work anymore. This is the code in OI:
• SET --- WIDGET NAME = *TBL INF02
  READ --- WIDGET HOLD 1 FT 0 BY WIDGET NAME
  T SET --- WIDGET WIDGET TYPE = TABLE
  T SET --- WIDGET D SRC AP = OTO
  T SET --- WIDGET D SRC INV TYPE = SUBPROCESS
  T SET --- WIDGET D SRC NAME = *TBL INF02
  T REWRITE --- WIDGET FAIL 0
• If a field has a size override >80 characters, the table will not display. Fields larger than 80 will display properly if there is no size override.
• Token fields do not work properly, doesn't display the token text, I get some other character, or the table doesn't display at all.
• The table widget is only suitable for displaying a relatively small number of records. Otherwise, the time needed to download the records to the client can get excessive. Records can only be loaded at a rate of about 2,000 records per second. Consequently, the table widget probably cannot be used as a record selector for larger records sets. For example, the time needed to load about 30,000 records is about 15 seconds.
• The table widget is always repopulated when returning from an optional child process. This can cause long pauses if the number of records included in the table is more than a couple of thousand.
• The mouse is the only way to navigate within a table widget. pgup, pgdn, cursor up, cursor dn, etc cannot be used.
• Columns sort based on the displayed value in a column, not the field values. For example, dates displayed as mm/dd/yy will not sort in date order.
• At runtime, a table widget never seems to keep the focus. When you select a record, the focus returns to the field which had the focus before you clicked to select a record.
• 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 Editor

• There should be a flag on the --- WIDGET spec to indicate if the field can accept a Drop action. This should be available for the following Widget types: button, label, table widget, html viewer, and Window Background. Currently only works for Widgets attached to a field on the image. * Fixed * There is now --- WIDGET DROP TARGET that marks a widget as able to receive a drop action. It also looks at --- WIDGET FI CHOOSE MODE to see what kind of Drop should be supported. --- WIDGET FI CHOOSE MODE has values of ANY, FILE, FOLDER, TREE where ANY is a single file or folder name. Many more widget types now support being a drop target, but still require a field on the image.

Drag & Drop Runtime

• There are times when it would be nice for the ADC Window to gain focus when an object is dropped on it. * Fixed * Client window now gains focus on a drop.
• Provide a runtime API to copy the --- DROP* files to memory versions of those files (MDROP* ?) to make it easier for a designer to save the contents of --- DROP.
• Files dropped remain in the temporary folder forever. They should probably be cleared when the --- DROP* files are initialized. Alternatively, provide a method for the designer to specify a location for dropped files, and the designer will manually clear the directory at login. Is this 'Fixed', now that there is a setting for dropCachePath?

New Event Points Editor (Tab In/Out/Value Changed)

• They only show up on the Alpha field GA, should be for any tabbable/modifiable field.
• check online help

New Event Points Runtime (Tab In/Out/Value Changed)

• Setting the flags via ILF on non RAW TEXT widgets does not cause the events to fire. Probably should fire for all modifiable/tabable widgets.
• It also seems like performing a shift-tab (going back to the previous field on the screen) does not work when your cursor is in a textfield with multiple rows.

Better Error/Warning Control Runtime

• If >1 ERROR message, color coding is lost (does not appear in Red). Check Warnings/Messages for the same problem.
• The Control-M display no longer color codes the messages (It used to in an earlier version, I think).

Better HTML Widget

• VLC option does not work - * Fixed once I properly installed VLC *
• line breaks not honored in javascript viewer * Fixed * seems to work for me now.
• Need proper Widget attributes vs @SHTML= * Fixed * Now have CODE VIEWER, HTML EDITOR, FLASH PLAYER, MEDIA PLAYER, WEB BROWSER widget types on Text fields. Also, CODE VIEWER looks at --- WIDGET CONTENT TYPE to see what syntax highlighting to do. WEB BROWSER looks at --- WIDGET SHOW DECORATE to see if it should show it's Web Browser controls or not.
• Does this replace the old HTML Viewer? - No, the old HTML viewer is still available.
• Praclox Web Page not rendered correctly. Compare Appx client version to web page in IE, notice Praclox banner at top of page missing.
• 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 tired 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.
• APPX should store HTML text without modification. e.g. Don't translate LF to paragraph characters. APPX should also pass stored text to the editor without modification. The purpose of the HTML editor is to create and edit HTML text. APPX should not modify the text that is created by the editor.

Add Mode No Longer Clears Screen

• Cursor is moved to bottom of display instead of inserting a record at current location - Need to look into this more. Some screens adding at the bottom seems like the expected thing. Others not so much.
• Some scrolling inputs in 0AD (Fields, End User Selections, Designer Selections, others?) attempt to position the cursor just after the file name. They expect the screen to be cleared, so now they position the cursor on the wrong row.

Client Window Sizing & Scaling

• resizeMainWindowPane can be set to "true" to turn on the option to automatically resize the client window to fit the current frame/image size.
• resizeMainWindowPane need to be moved out of the Experimental section of the Client Preferences
• The other functionality described in feature 44 has not been implemented

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.

Other

• Need .WIDGET routine to REFRESH Table Widget via WIDGET VISIBLE INIT, maybe?. * Fixed * Now have field --- WIDGET RELOAD DATASRC as a widget field that if set to Y in Option Intercept will cause the Table widget to reload it's content even though it may not go to Pre-Display. There is also a new subroutine called .WIDGET RELOAD DATASRC that if passed a Widget Name will set the field with much less ILF code needed. You can also pass it two widget names and it will BEG AT and END AT on the two names and set all the widgets it finds.

Comments:

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

-- JeanNeron - 2012-06-14