Description


Saving grid status (KeepLayoutState / LayoutStateStorage) column size = 0 should be considered a valid layout size.

Use Case


As of 9.6.07.X704 saving grid status is properly enabled in different contexts with various modes, but column size 0 (zero), either defined from enduser collapsing a column or managed from the code, is NOT considered a valid layout size but a syntax size and is NOT saved. It should be considered valid and saved as layout size! When in a later session a grid layout saved is restored a column with size equal 0 (zero) should be considered available but hidden in the exact position like it was when saved; there should be a way for the enduser as well as by code to restore it to a size greater than 0 (zero).

Importance


Medium

Type


Uniface 4GL

Operating System


Windows

Status


2 thoughts on “Grid widget enhancement”

  1. “There should be a way for the end-user to restore it” is the mayor issue here.
    The issue has at least 4 parts:
    – How can the user see that there is a hidden column that he/she can restore?
    – Do we want a column that was hidden by Proc to be visible as a restoreable column?
    – What action do we want the user to take for a restore?
    – Do we allow a user restore on a column hidden by Proc?

  2. (Theo Neeskens wrote:) The issue has at least 4 parts:
    1 – How can the user see that there is a hidden column that he/she can restore?
    a) Basically if he/she have hidden the column before it should remember it…and restoring with a mouse action opposite to the one used to hide
    b) For users and mouses without memory or if restore action described at #1 could not be implemented, Uniface should provide an added functionality to grid, like clikking on the upper left square (origin) of a grid to show a list of available columns with a checkbox for each one defining visibility status. The user could restore hidden columns from there.
    2 – Do we want a column that was hidden by Proc to be visible as a restoreable column?
    We need three different visibility statuses: visible, normally not visible (by user or by code), deeply not visible (only by code)
    3 – What action do we want the user to take for a restore?
    See previous answer #1…only normally not visible columns could be restored from there, NOT deeply not visible columns!
    4 – Do we allow a user restore on a column hidden by Proc?
    It should be possible for developers define if endusers can or cannot restore a column as visible, see previous answer #2…

Leave a Reply