Idea Delivered Partially

A significant number of system variables were added in XPP 9.5. Please refer to the XPP 9.5 Release Notes for further information.

Enable access to ALL system and frill variables

While there are pages and pages of system and frills variables, there are still many missing.

When viewing the Status Window, there are many attributes and dimension values that are not accessible via the % or ! variables.

E.g.   !tbcypos - tabular cell y position.

Strangely, there IS tbcxpos - but not the ypos?

Rather than list variables that aren't present, it would be easier to simply make ALL Status Window values available as % or ! variables.

  • Wish you had opened a new Idea; might be hard to track this new request here in an Idea that is already "Partially Delivered". I don't know how the "voting" for this new request would be distinguished from the previous request. But maybe it's possible ...

    Other thought I had on this request was that there are actually two kinds of "header" rows.

    There are the "style" header rows, determined by the Number of Header Rows field in the T1 spec. These are the rows that are shown as "H#" in Table status and to which the (row) styling fields in the T5 spec apply.

    Then there are the "continued" header rows, determined by a different Number of Continued Rows field in the T1 spec. Those are the rows that repeat when a table breaks.

    Often times the number of "style" and "continued" rows are the same, but they don't have to be (as there are these two separate values that control them).

    Which "kind" do you want/need a variable for, or do you want a variable for both kinds?

  • Another variable that still needs to be added to the list is one that identifies whether the current row is in a header row or not (and therefore implies in a body row).

    This is not the same as the current variable that indicates whether the row is in a continued header (tbrhd).

    While using frills processing, it is necessary to know whether the current row is within the header or not. 

  • Apologies for the late reply!

    Here's my list. There's no real priority amongst the items as I need them all

    >>  !tbcypos (as mentioned in previous messages, there is !tbcxpos, but not matching !tbcypos)

    >> !tbctrule and !tbcbrule (there are tbclrule and tbcrrule)

    >> !tbctgut and !tbcbgut (there are tbclgut and tbcbgut)

    >> !tbctwsp and !tbcbwsp (there are tbclwsp and tbcrwsp). Just as expanding the column and/or box gutters adjusts the tbclwsp and tbcrwsp, the top/bottom white-space vars should reflect the cell's gutters with/without row justification.

    Basically, filling in some blanks, where the left/right variables exist but the top/bottom don't.

    I'll add some more as and when I find them missing.

    PS. I've got around these by complex calculations which slow frills composition (actually, the composition process is simply waiting for Perl to finish, but the Perl calculations are complex and take their time when dealing with large tables with many columns/rows).

  • Again, Mark, what we were hoping for is a prioritized list (from at least you, since you initiated this Idea, and at one point you said you would provide such a list).

    If you throw a list of 100 things to do at us (or anyone), it's human nature to just ignore it altogether - it's too big of a task to scope out or be able to "spend" resources to do.

    If you threw that same list at us but broke it down into a prioritized list, or even better as a list of shorter groups of "tasks" (or missing variables) in order of priority, then we would be more likely to task it out in those smaller chunks (as development tasks) - and at least address some of the highest priorities and perhaps over time be able to "spend" the time to get to others.

    Anyone else want to chime in with their prioritized list (or "groups") of "missing variables" that they would like to see added to XPP?

    Jonathan Dagresta
    SDL XPP Engineering