Well it seems I broke stuff, this time with the picture of my uploaded module. It doesn’t display it and when you to to the actual file it gives a NotSupportedException or this one :) My original picture has a size of 558 x 173 (not sure if this is important in any way).

@strawberry-3.141 I didn’t want to spoil the fun of learning it :) :P

@shashank Hmm odd, what did you see on your screen and what config did you use?
This should work just fine:

    modules: [
        {
            module: "alert"
        },
        {
            module: "MMM-ProfileSwitcher"
        },
        {
            module: "MMM-TouchNavigation",
            position: "bottom_center",
            classes: "default everyone",
            config: {
                buttons: {
                    "default": {
                        symbol: "ban"
                    },
                    "Brian": {
                        text: " Brian",
                        symbol: "paper-plane"
                    },
                    "Lisa": {
                        text: "Lisa"
                    }
                }
            }
        },
        {
            module: "clock",
            classes: "everyone",
            position: "top_left"
        },
        {
            module: "clock",
            classes: "default",
            position: "middle_center",
            config: {
                analogShowDate: false,
                displayType: "analog"
            }
        },
        {
            module: "helloworld",
            classes: "Lisa",
            position: "lower_third"
        },
        {
            module: "helloworld",
            position: "top_right",
            classes: "Brian"
        }
    ]

Edit: I added a ready-to-use config file in the repository. If you copy-paste and rename it it would work.

@shashank You’re welcome!
@chrisyy you can use front awsome by setting the class of the symbol’s container to fa fa-symbolname. Something like this (where symbolName can be any icon name):

var symbolName = "paper-plane";
var symbolContainer = document.createElement("span");
symbolContainer.className = "fa fa-" + symbolName;

Note: I tested it with electron and firefox

@strawberry-3.141 Checked it, what happened was that this transition style was added as expected. However what I did notice was that the container within a region also changed it’s display value. When hiding it was set to display: none; after the animation. When showing a module it was set to display: block; and right when that happens the module is visible without animation (eventhough the module’s container did change transition value)

I tested this with the remote controll module aswell and experienced the same result.

When calling the show function from a module it doesn’t use it’s animation, no matter the animation time. I am using windows and just did a clean pull to make sure it wasn’t the fault of a module I was making.
To test this I made a very simple module, code:

Module.register("TestHideShow", {
    notificationReceived: function (notification, payload, sender) {
        if (notification === "TEST_HIDE") {
            MM.getModules().enumerate(function (module) {
                module.hide(10000);
            });
        }

        if (notification === "TEST_SHOW") {
            MM.getModules().enumerate(function (module) {
                module.show(10000);
            });
        }
    }
});

All it does is hide all modules when a notification is recieved.
Then I copied the sample config, removed both weather modules and added:

{
    module: "MMM-ModuleScheduler",
    config: {
        notification_schedule: [
            {notification: "TEST_HIDE", schedule: "3 * * * *", payload: "a"},
            {notification: "TEST_SHOW", schedule: "4 * * * *", payload: "b"}
        ]
    }
},
{
    module: "TestHideShow"
},

I used the ModuleScheduler to send 2 notifications, with one minute in between.
For the hide animation everything works as expected, a very slow fade out (10sec). Then after one minute you would expect a very slow fade in (also 10sec), but it just pops onto the screen as if the duration was 0. I also checked the log and it didn’t do anything unusual.

Is anyone able to recreate this/does anyone encountered the same issue?

Note: I came across this while making a different module, so it’s not because of this testing module only.

@in_a_days put the names you want in an array, like so:

var exceptClasses = ["clock", "weather", "calendar"]; //The list of modules you want to keep.
MM.getModules().exceptModule(this).exceptWithClass(exceptClasses).enumerate(
    // Here the other code
);

@all, I made a module which is similair to this one. In mine you can set custom profiles and swap between them. Hope that this helps one of you guys :)