ALT not doing anything

ankonaskiff17

@sdetweil This is in regards to auto-starting MM.
When installing NPM per the documentation, do you install at ~$ or at/MagicMirror $
It isn’t real clear because half way through that sequence it has cd ~ which you could take to mean you are installing npm at the MagicMirror level then you back up to put the auto start script at root?

I kinda-sorta think I understand what is going on with this ALT problem but I’m out of gas and will confirm in the morning.

sdetweil

@ankonaskiff17 npm is installed globally (-g)
effectively as root… system wide

the pm2 install for auto start is to execute the command output from the command, pm2 startup

and npm (node package manager). is what loads the dependencies listed in package.json (npm install) and then executes the command listed in the scripts section of package.json (npm start, or npm run xxxxx, see the list)

I posted the command line parms to launch chromium instead of electron, so try that and see what keyboard handling there is…

ankonaskiff17

@sdetweil It’s alive.

sdetweil

@ankonaskiff17 which. prior, this w chromium, it’s Tuesday?

ankonaskiff17

@sdetweil I took two identical Pi 4B’s, formatted them intalled 64 bit PI OS on both.
Then installed MM 2.22.0 on one and 2.23.0 on the other.
No VNC or SSH, start to finish.

2.22.0 I hit ALT (only) and the expected toolbar with VIEW then Toggle Full Screen and the Open Developer Tools come up as I am accustomed to.

2.23.0 exhibits that same unexpected behavior that started us down this road.

The whole ALT+F11 is WAY WAY beyond me but it does shrink the size of the MM overlay. Unfortunately it does not give you Open Developer Tools so that is a problem.

Beyond that, I am clueless. Why 2.22.0 works as desired and 2.23.0 doesn’t is way out beyond my level of knowledge.

I never got to the Chromium stuff you described but more than happy to run that down on the Pi with 2.23.0 on it.
Once I saw that 2.22.0 install give me what I wanted I was going see if I could repeat that.

sdetweil

@ankonaskiff17 yes, the electron version changed between 22 and 23…

so, we are back to the original statement… something changed in electron…

ankonaskiff17

@sdetweil You won’t get any argument out of me on that score.
As I said, glad to help if I can just as long as you tell me what to do.

ankonaskiff17

@sdetweil I’m calling it a wrap for today but is there a way to make the developer tools to open that is not “open developer tools”?

I did something yesterday and that launched but when you move the mouse around it is like it is behind the MM window. If it wasn’t doing that you could right click page and bring that up up.

Reason I ask is I did see some Electron errors yesterday but I’ve seen them in past so I just ignored.

ankonaskiff17

@sdetweil Can you tell me how to easily capture/install the prior 2.20.0 version ether direct to the Pi I want to install MM on. I have two upcoming MM projects and while the one Pi is ready, it is going to be a simple build as far as MM’s go so will knock it out pretty quickly.

I have successfully installed that earlier version twice but still way more hunting and pecking than is desireable. Plus it would be good to know more generally.

Is sudo rm -r MagicMirror the best way to remove the problematic 2.23.0version? That is what I have been doing and since I have only just installed MM and no modules it seemed like that would do what I needed.

sdetweil

@ankonaskiff17 you can rename it

mv MagicMirror new_name

later rm -rf MagicMirror to delete it
I posted on the github issue on how to git clone a tag
and where to find the tags
each release is saved as a tag