Yet another unintuitive Cognos 'feature' that has wasted hours of my time.
I have a 2 column, 3 row table on my prompt page. Each cell has a 1 column, 2 row table that includes a Value Prompt and text item above for user instruction.
The column width default to take up the whole screen. I want to minimize this so it looks more professional.
Here's what I'm doing that does not work:
1.) Select each cell in the 2x3 table columns
2.) Size & Overflow > width = 300px
Result: NO CHANGE.
WHY? HOW DO THESE SIMPLE TASKS BECOME FRUSTRATINGLY TIME CONSUMING ENDEAVORS IN COGNOS
Quote from: psrpsrpsr on 23 Feb 2018 09:20:20 AM
Yet another unintuitive Cognos 'feature' that has wasted hours of my time.
I have a 2 column, 3 row table on my prompt page. Each cell has a 1 column, 2 row table that includes a Value Prompt and text item above for user instruction.
The column width default to take up the whole screen. I want to minimize this so it looks more professional.
Here's what I'm doing that does not work:
1.) Select each cell in the 2x3 table columns
2.) Size & Overflow > width = 300px
Result: NO CHANGE.
WHY? HOW DO THESE SIMPLE TASKS BECOME FRUSTRATINGLY TIME CONSUMING ENDEAVORS IN COGNOS
What is the size and overflow setting for the 2x3 table? Tables default to 100% width.
You're correct, it is at 100%. What is order of precedence by which tables expand width? For example, if the highest level container is set to 100%, so no sub-level objects or cell width properties will be followed?
What are best practices in terms of page design when it comes to certain properties taking precedence over others?
Thanks!
Quote from: psrpsrpsr on 26 Feb 2018 08:17:48 AM
You're correct, it is at 100%. What is order of precedence by which tables expand width? For example, if the highest level container is set to 100%, so no sub-level objects or cell width properties will be followed?
What are best practices in terms of page design when it comes to certain properties taking precedence over others?
Thanks!
When you create a table there is a checkbox "Maximize width" that is selected by default. If you uncheck the box the table will not be created with 100% width. You've probably seen that checkbox a thousand times but never really looked at it.
I suggest the best practice is to set properties at the highest level appropriate so that they are inherited by lower level objects. For example, if I wanted a particular font for all the cells within my table I'd set the font at the table level. If a cell within the table needed a different font for some reason then I'd set the font differently for that cell which would override the parent level font setting. If I decide to add more rows or columns to my table then text placed in these will automatically be styled with the font set at the table level. Alternatively, if I had chosen to select each cell in the table and set the font at the cell level then I'd also have to set that style on any new cells created when adding new rows or columns.
Size and overflow settings on cells within the table may be honored within the context of the overall table size and overflow where possible. For example, I can create a 100% wide table and then set all the cells in one column to a specific size. This will size that one column as I dictate, but the other column (or columns) will be sized to make up the remaining available width.