Help with updateDom

MMRIZE

After the module is started I get the data (takes a few seconds to return the data and this is where the initial problem is, I think).

The usual approach would be; Draw empty view and then when the real data is coming, redraw with updateDom().
It means… just put all the logic of updateWrapper into getDom. It would be more usual way.

Anyway, let’s see.

getDom: function() { 
  var wrapper = document.createElement("div"); 
  wrapper.id = "growatt-wrapper"; 
  this.wrapper = wrapper; 
  return this.wrapper; 
},

Everytime updateDom() is called, new element '#gorwatt-wrapper` is created. Current dom would be destroyed and replaced by that new empty element.

socketNotificationReceived: function(notification, payload) {
    console.log(notification, payload)
    if (notification === "GROWATT_DATA") {
        this.growattData = payload
        this.updateWrapper(this.growattData); 
        // Here you tried to draw your data, but...
    }
        this.updateDom();
        // Here your wrapper updated would be reset. So... How about skipping this?
},

Just skip updateDom if you don’t need it.

BTW, this.wrapper = wrapper might cause memory leaks. Storing id instead of domNode itself and revoking it on demand is better way.

this.wrapperId = wrapper.id
...
// in other place;
let wrapper = document.getElementById(this.wrapperId)

mumblebaj

@MMRIZE Thanks for the reply. Let me see what I can make of the suggestions. I know the approach is strange, but what I am trying to avoid is that when I start the mirror, all modules stay active on the 1st screen instead of hiding the modules I don’t want active on the 1st screen. I am using MMM-pages for this. Because there is a delay in the data being returned it causes this issue.

mumblebaj

@MMRIZE I made some changes and it runs nicely now alongside the other modules. However, when the data refreshes it creates new elements instead of just updating the existing ones.

As you can see the down arrow is duplicated and so are all the other elements. This is because of the way the module is structured. I have some ideas now of how to fix it though.

Thanks for the help. Other suggestions are welcome. :winking_face:

sdetweil

@mumblebaj you don’t HAVE to create new elements on refresh, save the wrapper div and it’s tree.

check on next getDom if it exists and do whatever to update

I do this on a few to eliminate the flash of content change. I only ever build the content in getDom()

updateDom() is just the trigger to mm to call your getDom() to get new content

MMRIZE

@mumblebaj said in Help with updateDom:

but what I am trying to avoid is that when I start the mirror, all modules stay active on the 1st screen instead of hiding the modules I don’t want active on the 1st screen. I am using MMM-pages for this. Because there is a delay in the data being returned it causes this issue.

Hmmm. I think hiddenOnStartup option of the module configuration would be what you really consider.

sdetweil

https://forum.magicmirror.builders/uid/6639 also. you don’t HAVE to show any content. you can return an empty div and mm is happy

you should also keep track of your hidden state (suspend/resume) and not call uodateDom while hidden… so u won’t generate any content while pages has u hidden

mumblebaj

@sdetweil The biggest issue is that I need to set arrows based on data being returned. I.e. Arrow will go up depending on the data or it points down based on the data. That is where I am stuck. How do I set those back into the wrapper based on the data.

generateSolarLine: function() {
    var ppvData = parseInt(this.growattData[0].ppv1) + parseInt(this.growattData[0].ppv2);
    solarLabel.innerHTML =  `Solar: ${ppvData}W`;
    if(ppvData > 0) {
        solarLine.classList.add("active");

        const solarArrowOut = document.createElement("i");
        solarArrowOut.classList.add("arrow", "down", "active");
        solarLine.appendChild(solarArrowOut);
    } else {
        solarLine.classList.add("dimmed");
    }
    return solarLine;
},

Bases on the value of ppvData I am setting which way the arrow points etc. Doing all the work in the getDom gives issues

sdetweil

@mumblebaj

save solarArrowOut as a module instance variable and redo it’s attributes when u need to.
instead of creating it fresh ever time

this means all the stuff around it should be stable too…

mumblebaj

@sdetweil Thanks Sam. Managed to resolve this. Everything works fine now and plays well with the other modules.