Keynote Legend Format

[RJSNZ]

It seems like in order to set out a legend using all keynote elements (key/title/description/reference) you must use a 4 column format. (3 if you exclude reference)

When your title and reference is long this seems extremely space inefficient on a layout.

Is there a way to organize the legend into 2 columns or even 1 and still show all the information?

option 1: (my default layout with CI Keynotes - Sample image attached)

Key : Title
        : Description
        : reference (?)

option 2:
Key : Title
Description
reference

It seems that this library object needs to have more flexibility in formatting and displaying of information:

Operating system used: Windows 10

[James B]

Thanks for the feedback, currently you can merge cell content into one cell, but at the moment it will separate with a space only - not onto new lines and having separate formatting as per your example.

We have been investigating this further though.

[RJSNZ]

I just want to add to this in case the development team follows these threads.

Additional comment:

Table format / Table Style uses Max. Number of (table) Rows to set how far down the page a schedule will run.
This seems to be the only method to ensure your schedule does not over run a page (or the allocated space)

However in practice the lines in each row is not taken into account so if i set 60 rows, then one column could have 120 lines and another could be the minimum 60. This means a table with multiple columns appears inconsistent on a page.   

 

[James B]

Thanks for sharing the example and feedback.
The control is based on table rows, not text lines, as the gdl doesn’t know many lines of text is or isn’t being gathered. What might be possible, is to have a control for each column perhaps - I’d have to check if this is possible. In AC29 we have been working on a few other improvements for the legend, such as background colour, further control of merging columns and customising text.

[RJSNZ]

Thank you.

Ideally, instead of counting multiple column rows and having individual settings per column, having a setting to limit the maximum table/column height would be the best solution from a drafting perspective. 

If a note "cell" cannot fit in the space allocated then it goes to the next column stack.

I expect counting rows would be a tedious task for users especially if there are edits later in the content of the cells as a project progresses through a contract.

In addition another minor improvement would be a spacer setting in each cell, similar to the setting AC uses for Text Contour Offset.
You will see in the example image that I was using horizontal lines between rows as there was no ability to visually space notes in the the schedule (without resorting to blank line in the text itself) .

Or perhaps an alternative solution would be to allow the option to insert a blank row between every note (with a customized height setting) when generating the schedule.