[claudiobosticco]

Hello, my full use case is closer to the following:

isc.Calendar.create({
    ID: "aCalendar",
    width: "100%",
    height: "100%",
    autoFetchData: false,
    dataSource: "supplyItem",
    autoDraw: false,
    currentViewName: "month",
    startDateField: "nextShipment",
    implicitCriteria: {
        _constructor: "AdvancedCriteria",
        operator: "and",
        criteria: [{fieldName: "nextShipment", operator: "notNull"}]
    }
});

isc.AdaptiveMenu.create({
    ID: "adaptiveMenu",
    menuButtonTitle: "More...",
    align: "center",
    defaultLayoutAlign: "center",
    items: [
        {
            title: "Foo Bar",
            icon: "Edit"
        },
        {
            title: "Foo Bar",
            icon: "Edit"
        },
        {
            title: "Foo Bar",
            icon: "Edit"
        },
        {
            title: "Foo Bar ",
            icon: "Edit"
        }
    ]
});

isc.ToolStrip.create({
    ID: "aToolStrip",
    // height: 32,
    width: "100%",
    layoutMargin: 0,
    defaultLayoutAlign: "center",
    members: [
        adaptiveMenu
    ]
});

isc.VLayout.create({
    ID: "aVLayout",
    visibility: "hidden",
    border: "2px solid blue",
    width: "100%",
    height: "100%",
    members: [
        aCalendar,
        aToolStrip
    ],
    autoDraw: false
})

isc.HLayout.create({
    ID: "aHLayout",
    border: "2px solid red",
    width: "100%",
    height: "100%",
    backgroundColor: "white",
    members: [aVLayout]
})

(where aHLayout contains multiple layouts, but only one is visible at a time)

Then, if you call:

aCalendar.fetchData();
aVLayout.animateShow();

the fetch is not executed.

[Isomorphic]

Thanks Claudio - just confirming, we do see the issue and have a fix ready. However, while adding new autotests for these reports, we see some minor differences across different views and will be addressing those in the next day or two. We'll update here when the changes hit builds.