Display Column details in Form design (OpenInsight 64-bit)
At 05 APR 2020 09:16:18PM Gerry Van Niekerk wrote:
Hope everyone is keeping save
As we cant go anywhere it must be development time..
OI 10
When in form designer and adding or viewing an existing column detail,
It would be nice to see the column position and/or the first line for symbolic items..
Thanks
Gerry
At 09 APR 2020 04:36AM Carl Pates wrote:
Hi Gerry,
Something like this is probably better put in the suggestion box so we don't lose sight of it, but I do agree the Table/Column option editor in the FormDesigner needs improving.
At 09 APR 2020 08:20AM Mike Ruane wrote:
Gerry/Carl-
yeah, agreed. I've been doing more 10 development for a couple of customers, and I miss the 'Details' functionality.
Let me see what I can put in there….
Mike
At 16 JUN 2020 07:51PM Gerry Van Niekerk wrote:
Mike ,
Suggestion..
While looking at this can we add new dictioneries on the fly as well while adding a new prompt rather than having to open the table, same as in V9
Thanks
Gerry
At 17 JUN 2020 04:39AM Carl Pates wrote:
Hi Gerry,
I don't know if we'll ever put in direct column editing from a FormDes control property as the technical implications of maintaining that are not small (e.g. the table locking coordination and inter-designer notifications for a start).
When the IDE interface is finalized you will be able to have a side-by-side panel layout so that you can have your table open next to your form for example and you can edit directly in there. You can kind of emulate this at the moment if you open another IDE instance.
Regards
At 17 JUN 2020 05:06AM Gerry Van Niekerk wrote:
OK was only a suggestion
i can do it with the table open, but time consuming
I suppose its all about ease of use, will see if previous suggested changes was implemented
as creating a new form is not easy when linking dicts
Even the table doesn't default when selecting a dict item, just not as simple as V9
Sorry
Gerry
At 17 JUN 2020 06:08AM Carl Pates wrote:
Hi Gerry,
From what I can see I don't think any updates to the FormDes Column dialog are in the current build, so I'll see what i can do about that.
The fact that the table is not pre-selected is definitely a bug, and I agree that the dialog itself could be a lot better e.g:
resizable and remembering the size, and displaying column properties), but apart from adding new columns to a table or making direct edits to the column properties is there anything else that will improve it for you?
Regards
At 17 JUN 2020 06:30AM rdhull50 wrote:
Just to add my two cents, and I could be wrong … and there is a great probability that I am. I think I read that best practice is to include the description of a dictionary item in the Description field of the dictionary, I.e field 14. However, I don’t believe that is in the Dictionary design window.
I know that in AREV it was certainly most useful to have not only the description but the help text in dictionary field 14. So it would also be nice to have that added as a help property or option in the form designer. I can add that as an enhancement request … maybe I already did?
At 17 JUN 2020 07:03AM Carl Pates wrote:
Hi,
However, I don't believe that is in the Dictionary design window.Are we talking about the Table Designer? There's a "Description" property item as part of the column properties that updates field 14 of the column DICT record…
I believe your second point was about having a control property that shows the column Description (F14) as the default help entry for a data bound control at runtime yes?
Regards
At 17 JUN 2020 06:26PM Gerry Van Niekerk wrote:
Hi Carl,
I think a simple improvement that would help would be to see the position of the dict in the display as well
IE
I have a table with heaps of dicts and use it as a control record table
So when I do a new form for a new control record I know what position I want to use but cant always remember the dict name, so if the dict name and pos was there it would make a huge difference
For symbolics maybe the first line? not that important though..
As far as adding new dicts having the table builder open as well will suffice and would only be a back and forward thing with new tables and dicts, or when we add new dictioneries
Thanks
Gerry.