Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    getPrintHTML on Timleline results in error

    Hi there,
    I'm getting an error on the timeline when calling getPrintHtml on a timline.
    It seems that there might be a connection to "showControlsBar" whcih is set to false. Setting this to "true" results into the corresponding html.
    This is reproducable in SmartClient v121p_2022-04-05_Pro and also in the latest nightly SmartClient v121p_2022-04-07_Pro in Chrome 99.0.4844.51


    Code for reproduction:
    Code:
    isc.Button.create({
        "ID": "printButton_14",
        "click": function () {
            theTimeline.getPrintHTML({printForExport: true}, function (data) {console.log(data)});
        },
        "left": 100,
        "top": 100,
        "autoDraw": true,
        "title": "print"
    });
    isc.Timeline.create({
        "ID": "theTimeline",
        "width": "700",
        "autoDraw": true,
        "height": "80",
        "overflow": "hidden",
        "hideUsingDisplayNone": false,
        "hoverWidth": 200,
        "startDate": new Date(2022, 3, 4),
        "endDate": new Date(2022, 4, 1, 23, 59, 59),
        "headerLevels":
        [{
                "unit": "week"
            }, {
                "unit": "day",
                "headerWidth": 45
            }
        ],
        "showControlsBar": false,
        "showEventDescriptions": false,
        "laneFields":
        [{
                "name": "title",
                "title": "&nbsp",
                "type": "text",
                "canEdit": false,
                "escapeHTML": false,
                "shouldPrint": true,
                "editorProperties": {
                    "escapeHTML": false
                }
            }
        ],
        "lanes":
        [{
                "hierarchyLevel": 0,
                "isOpen": false,
                "height": 30,
                "name": "One",
                "title": "test"
            }
        ],
        "data":
        []
    })
    Best regards
    Simon

    #2
    hi Simon - thanks for the report - we've made a change to address this issue and you can try out the fix in tomorrow's builds, dated April 9 or later.

    Comment

    Working...
    X