Read the statement by Michael Teeuw here.
Debugging
-
That makes sense. So then I guess I have 2 questions leading on from that:
-
I’m attempting to create a dynamic 3d model but I need a height and width. Is there any way to retrieve the rendered height and width at runtime based on the resolution?
-
Using a browser to go to the rip’s IP via the MM port sounds useful. How do I retrieve the rip’s IP/MM port?
thanks again for the response
-
-
- Nope, or unknown rather.
- Check your router for the IP of the devices connected to it, or on the rpi, type
ifconfigat the prompt. If you’re connected wirelessly, look for thewlan0block. If it’s hard wired, look for theeth0block.
And if you have access to your router, it’s worth setting the rpi’s IP to always be the same.
-
Darn. That makes things a little more difficult.
Any advice on how to approach that then? Since I have a dynamic 3D object that needs a rendering size to construct.
I can keep it at a static size, allow config files to set it?.. Small, medium and large I guess?
-
This might help you: http://www.w3schools.com/jsref/prop_element_offsetwidth.asp
-
Or if you wish to run your module with jQuery, using .width() and .height() will also give you the size of the element.
-
Thanks for your response. I’m still working on it (and something else for another member) - I’m still having trouble accessing/finding a log. For the most part, right now, I’m running the npm from my computer directly and using the electron app there.
I’m not able to find any log file, or any tool that allows me to debug in real-time. Because of the nature of this app and the modules, it becomes a little more complex than just following instructions that I’ve seen/Any advice?
-
I guess I’m not sure what you mean with ‘real-time debugging’ as there is no real-time anything between the node server and the browser. Everything runs on the browser end, and because of that, you can open the console window and watch what’s happening, in as ‘real-time’ as possible. I’m also not sure what exactly you are trying to debug.
As I explained before, when I’m writing code, I watch the console log for errors. I simply refresh the browser when I need to check for things. Remember, I don’t use the actual Raspberry Pi nor the monitor connected to it to debug. I load up the mirror on a regular browser on my computer and debug there. I also write code there.
Hrm, it dawned on me that I should explain better how I’m doing this …
-
Even when writing console.log(’ ') nothing appears in the terminal, so I just assumed it was logging elsewhere.
How are you accessing it via your browser?
-
Nothing would appear in the terminal, it’s not the STDOUT facility that you’re using. The console.log() facility logs to the browser’s console log. With most browsers, you access this by pressing F12. This is what my desktop looks like when I’m coding. Note that this is a Windows machine with dual monitors. On the left monitor is my code editor, split into two panels so I can look at multiple files at the same time. The files are being opened directly from the MagicMirror folder on the Raspberry Pi. On the right is a Chrome browser open with the Raspberry Pi’s IP address. That loads up the mirror display. And by hitting F12, I get the console panel that you see open, and at the bottom you can see the debugging messages that I put in the code to track. I can write/change code in the editor, hit Save, then hit Refresh in Chrome and get instant feedback. All of that is completely independent of what’s actually being displayed on the Raspberri Pi’s monitor.
The panel also allows me to see the actual HTML being returned (by selecting
Elementsat the top.) So any code that I write, I can verify the HTML bit, and I can follow along with any errors or other messages that I put in the code. When the mirror code fails for some reason, I can look in the console and try to figure out where the error lies.
-
Your last post helped immensely! Thank you!
