Greetings,
Has anyone had any luck controling the width of the header on the columns. PRO IV is ignoring the display width, input width and gui width settings of the data field when creating the headings. Seems to get worse the smaller the column is.
I have a paging screen with one column that displays a 2 character state code... it's defaulting to 1 character and giving me an elipses (...) in the header and data. The next column is a 1 character type code. It 's displaying about 7 characters, header and data.
I have changed all the possible widths on the columns and it has absolutley no effect. Is this another VIP bug? Or is this actually supposed to work.
As usual, the PRO IV website itself is less than useless.
Thanks,
Tom
Sortable Column Heading - paging screen
Started by sebago62, Apr 06 2009 03:32 PM
3 replies to this topic
#3
Posted 14 April 2009 - 09:12 PM
Hi Tom
How are you setting the column headers - in logic using .ColumnHeader or in the Editbox properties, Label Tab Paging Column Header?
Does your paging cycle have smooth mode set?
Are the resizable and remember settings set?
How are you setting the alignments for the fields - logic or editbox properties?
It may depend on the release you're on. I'm on 5.5 Build 513 and had to figure out which to use and when.
My notes for Paging cycles are:
To use .SortOnColumnClick then all the fields need to have the .ColumnHeader values set.
.SmoothModeSwitch must be set to TRUE for the paging cycle
Clicking on a column header will re-execute the paging cycle with the appropriate sort key
Note : if .Scroll is undefined or set to "Classic" or .PagingModel is not set then .ColumnHeader is disabled.
If .Scroll is set to "Standard" or "Off" then .ColumnHeader is automatically enabled.
It may also be that the Scroll has to be set after Smooth Mode has been flagged as doing it in Logic On entry (to cycle) gives a run-time failure (for the scroll)
See Page 63 and 82 of the Properties manual (printed page numbers)
See pages 64 and 144 of Properties Manual (printed page numbers)
(For more Information see Native Development Guide pages 89/90)
It was such a hassle using paging screens to display data that in most cases Listboxes are used. They're simpler to create, simpler to maintain and if generated as a global can be re-used elsewhere throughout the system.
Hope the pointers above help in some way.
Donald
How are you setting the column headers - in logic using .ColumnHeader or in the Editbox properties, Label Tab Paging Column Header?
Does your paging cycle have smooth mode set?
Are the resizable and remember settings set?
How are you setting the alignments for the fields - logic or editbox properties?
It may depend on the release you're on. I'm on 5.5 Build 513 and had to figure out which to use and when.
My notes for Paging cycles are:
To use .SortOnColumnClick then all the fields need to have the .ColumnHeader values set.
.SmoothModeSwitch must be set to TRUE for the paging cycle
Clicking on a column header will re-execute the paging cycle with the appropriate sort key
Note : if .Scroll is undefined or set to "Classic" or .PagingModel is not set then .ColumnHeader is disabled.
If .Scroll is set to "Standard" or "Off" then .ColumnHeader is automatically enabled.
It may also be that the Scroll has to be set after Smooth Mode has been flagged as doing it in Logic On entry (to cycle) gives a run-time failure (for the scroll)
See Page 63 and 82 of the Properties manual (printed page numbers)
See pages 64 and 144 of Properties Manual (printed page numbers)
(For more Information see Native Development Guide pages 89/90)
It was such a hassle using paging screens to display data that in most cases Listboxes are used. They're simpler to create, simpler to maintain and if generated as a global can be re-used elsewhere throughout the system.
Hope the pointers above help in some way.
Donald
Half of what he said meant something else, and the other half didn't mean anytthing at all
Reply to this topic
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users