Module Border Removal Issue

matt216

@sdetweil said in Module Border Removal Issue:

yes, and it really eliminates the ‘try this, nope, try this, nope… loop’

Doesn’t it! Waiting for pm2 restart mm each time was driving me nuts!

sdetweil

@matt216 said in Module Border Removal Issue:

Waiting for pm2 restart mm each time was driving me nuts

you don’t have to do a full restart,

change custom.css and hit f5 in the dev window, or ctrl-r on the MM side

so the cycle

start MM, npm start dev
or ctrl-shift-i if already running

use the elements tab to locate the html entry, which will expand the css class tree on the right
select the element u want to change (select pointer to left of elements page

edit the styles, upper right to get the effect u want

select/copy
alt-spacebar, n to minimise MM window

use your editor to add/change entry custom.css
using class name found in dev window
paste

save
click on taskbar mm entry to resurface page
ctrl-r or f5 to refresh page, reloading custom.css

check results…

ankonaskiff17

@sdetweil This a follow-on question regarding developer tools while MM running. If you have a module that is updating at a rapid pace it gets to be a real challenge trying to drill down to the lines you want to look at because at each cycle it will close all the expanded subsections. Is there a way to stop that other than setting a large update value?
Seems like it was either stock ticker or news ticker were culprits as rest of modules like calendar you can update every 12 hours or so.

sdetweil

@ankonaskiff17 no, they recreate the output every time, so you have to slow them down…