| | Known Issues
Table Widget Editor
- should only accept table source inputs (allowed me to enter a file name) * Fixed *, there was no editting on the fields at all. Made AP & Process name required fields.
|
| |
- Accepts Invalid field names, accepts invalid occurrence numbers, Does not automatically check app --- if field not found in current app, Scan for field names does not work. * Fixed * There were edits in there, but they were conditioned on --- ERRORS = 0, so once one error occurred, no further editing was done. Created new sub ITEM (EDIT FLD) (TABLESOURCE), based on ITEM (EDIT FLD), which validates field names, occurrences, field types (GROUP fields not allowed), Domains, and checks 0LA if not found in current ap. Replaced all editing with this new routine.
- Changes made may or may be not logged in SCCS, needs to be tested. Probably shouldn't fix this unless the Design Transfer problem is also fixed. Will likely have a ripple effect in SCCS re: closing tasks, etc. * Fixed * Was logging at the PROCESS level, but not the ITEM level. Tested locks, intent locks, color coding, task closing & design xfer.
- Can't change mask if field is not in the current application - * Fixed *
|
|
<
< |
- Can't run this process via Opt 99. In theory, you should be able to run this process by itself to test your ILF code in SOP, EOP, Post PCF Read, etc. The 0AD INVOC PROC process has no way to invoke a TABLESRC process type, since there is no ILF verb for TABLESRC (as there is for INPUT, OUTPUT, QUERY, etc). Or, to put it another way, we need a TABLESRC ILF command. This will affect the x-ref processes, so they will need to be made aware of this new verb. * Can you do an Opt-97 to build the EM? You can't run a FILE process directly. I'm not sure running a Table Source process standalone has any value. But I could be wrong (pete) * Yes, you can use Opt 97, I added all those helper options to the input. You can always run the input that uses the Table Source to step thru the code, so maybe this could be deferred for later. I was just thinking of consistency, Opt 99 always let's me run a process, even queries (Jean).
|
>
> |
- Can't run this process via Opt 99. In theory, you should be able to run this process by itself to test your ILF code in SOP, EOP, Post PCF Read, etc. The 0AD INVOC PROC process has no way to invoke a TABLESRC process type, since there is no ILF verb for TABLESRC (as there is for INPUT, OUTPUT, QUERY, etc). Or, to put it another way, we need a TABLESRC ILF command. This will affect the x-ref processes, so they will need to be made aware of this new verb. * Can you do an Opt-97 to build the EM? You can't run a FILE process directly. I'm not sure running a Table Source process standalone has any value. But I could be wrong (pete) * Yes, you can use Opt 97, I added all those helper options to the input. You can always run the input that uses the Table Source to step thru the code, so maybe this could be deferred for later. I was just thinking of consistency, Opt 99 always let's me run a process, even queries (Jean).
|
| |
Table Widget Runtime
- double click option difficult to trigger * fixed * Now using desktop double-click value.
|
| |
-
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.
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.
|
>
> |
- 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.
|
| |
- 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.
|
|
<
< |
- There's no WIDGET TYPE for the VLC Viewer
- WEB BROWSER does not show Web Browser controls even if --- WIDGET SHOW DECORATE is Y
|
| |
- Praclox Web Page not rendered correctly. Compare Appx client version to web page in IE, notice Praclox banner at top of page missing.
|
|
<
< |
- CODE VIEWER does not appear to do anything. Using old @SHTML= method works.
- HTML EDITOR does not appear to do anything. Using old @SHTML= method works.
- MEDIA PLAYER opens media file in a separate VLC window, old @SHTML= plays it in the Appx client window.
- You can look in 1EX (JPN) HTML CONTROL TEST to replicate the above issues with WEB BROWSER, CODE VIEWER, HTML EDITOR and MEDIA PLAYER. HTML CONTROL TEST in same App has the old method, which still works.
|
>
> | |
| | 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.
|
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.