| | 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.
- 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.
|
| |
- Filling dead space - right now the last column is expanded –if necessary- to create a row that fills the total with of the table, but that sometimes gives trouble in resizing the last column. ** Fixed **
- Wide Columns appear to be truncated. Try to display a 512 character field. ** Fixed **
- If there are compile errors in the Table Source, they are not displayed. Instead the default display for the Table Widget is shown.
|
|
>
> |
-
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 an item. Problem: Some of those widget types do not fire an option, ie, labels, etc. * 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.
|
| | Better Error/Warning Control Runtime
- In client preferences, the messageComboRows shows a default of 0, but it seems if there are >8 messages, a scrollbar is added. Default should show as 8? ** Fixed **
- Transitory messages (like process name during Em compile, restructuring, etc) no longer appear in the status bar.
|
|
>
> |
- 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 .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.
- Drag & Drop libraries are not installed during client install
- Mac (and probably Linux) clients do not run
|
|
>
> | Installation
- License agreement still refers to 5.1.
- Client does not run, fails with missing libaries
|
| | Comments:
Read what other users have said about this page or add your own comments. |
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.