Better picture, having set up client/server:
Read the statement by Michael Teeuw here.
Posts made by DarrenHill
-
RE: MMM-network-signal - make the message text larger
-
RE: MMM-network-signal - make the message text larger
@sdetweil I’ve dug a bit deeper and can see that the custom.css is there, but seems to be being overwritten (it’s crossed out)?
Here’s a screenshot of the mirror (apologies for quality, it’s via phone). Can you guide where I should be looking or clicking for this?
-
RE: MMM-network-signal - make the message text larger
@sdetweil I’m not sure I’m doing this right.
I’ve pressed ctrl+shift+i and got the inspector window up, then selected the elements tab (although it’s the default selection anyway) then clicked on the mouse pointer icon at top-left and then clicked onto the message text in the main mirror window.
When I do that I get the sub-window at the bottom of the inspector with div and P tabs, with the P tab selected. There I can see element.style with the text-align and font-size sub-entities plus user agent and main.css items.
P I take it from the code is the paragraph entity I need to be resizing, and from the top of the code the module name is .MMM-network-signal but it’s the rest of the top line to go into custom.css that I’m struggling to identify.
I’m not sure what you’re referring to by top-right box? I can see an icon for a computed styles sidebar, but there’s nothing much in there that isn’t in the other window area? This is on a Pi3 in a PiTop Ceed, so whilst I have keyboard/mouse connected up, my screen size is not so large to display everything without restricted menus (so I might be missing something here)
-
RE: MMM-network-signal - make the message text larger
@sdetweil I can see the two entries (text-align and font-size) in there under element.style when I select the message text.
I’m not sure how this helps us though? Is that what I should be looking to find, the element.style tag?
-
RE: MMM-network-signal - make the message text larger
@sdetweil said in MMM-network-signal - make the message text larger:
.MMM-network-signal p {
fontSize: 1.5em;
}Thanks for the suggestion Sam. Unfortunately when I added that to custom.css and restarted, I’ve still got microscopic text :(
I also tried font-size: instead of fontSize: (like other css items I have in there, and like in the js file) but that doesn’t work either.
-
MMM-network-signal - make the message text larger
I’m trying to adjust MMM-network-signal to make the message text larger. At the moment it’s at 0.65em, which on my mirror is microscopic.
I can see that it’s set in line 58 of the js file (see here ), and if I do a test with manual editing it works fine.
But I’d like to override it with a custom.css entry instead, but I’m struggling to work out what the syntax would be for that specific item.
Can someone give me some pointers as to what the entry in custom.css would need to be to override the 0.65em to 1.5em?
-
RE: Weather not Loading
@Cyric - You’re welcome.
I did the same update myself this morning, so know what needed to be changed…
Don’t forget to mark the issue as solved.
-
RE: Weather not Loading
@Cyric The new module uses apiKey rather than appid in the config. Try changing that in each entry.
-
RE: Merge conflict after update to 2.19
@sdetweil Good to know.
git status got me out of it, as I think things got out of sync rather than really needing merging or proper tracking (if subsequent research on what package.json actually means and does).
But useful to know how to actually see the differences for future reference. I really need to get more skilled-up on GitHub, but it always defeats me as I’m only an occasional hobby programmer for personal usage rather than for sharing/collaboration.
-
RE: Merge conflict after update to 2.19
@sdetweil Yes, I’m not quite sure what the weatherforecast.js change was, but that’s blown away now. As you say, the new module is fine with a little tweaking via custom.css.
It was the package.json file that screwed things up, and that I know I have never touched and have no idea what it was and why it got out of sync.
Anyway I learned a bit of stuff about GitHub and stashing, so that’s a bonus and we’re up and running again fine (after swapping out the depreciated weather modules too).