@sdetweil said in Electron v20 will coming with next release but...:

@kayakbabe where do you see 12?

all is ok to 19

https://github.com/fivdi/epoll/issues/42
Top comment by David

@lavolp3 said in Keyboard:

Then, AFTER the DOM element is created, you can create the keyboard class. I did this as soon as a text field was clicked on. With this method I can make sure that the DOM is created already:

I know it’s 2 years later, but that is what the MM notification DOM-OBJECTS-CREATED means… .

@arora1mayank said in controlling VLC by gestures:

gestures using raspberry pi camera did anyone tried i want to do help me

Learn how to access the Raspberry Pi camera and and video stream using Python and OpenCV. Capture images and videos using your Pi, Python

Thank you very very much

in my Galaxy S20 phone, I use the Shareit for transferring my data. You should use it…

Not directly.

MMM-ProfileSwitcher, A Profile/User/Layout Switching Module might give you a way of rigging it up.

Check module directory.

@jer78 If you are still looking to get this configured see this thread here. I had (what I believe to be) the exact same request and I got it working with this.

https://forum.magicmirror.builders/post/38213

@Krato5 I’m a little curious about the use case here, why would you want buy/sell buttons? Are you planning to make trades whilst brushing your teeth, or while getting dressed?

If I’m not totally mistaken, this module does not only check for updates of MagicMirror itself but also all other used modules. Maybe one should make this clearer in the description/Readme. I was a bit surprised to suddenly see several git-remote-http-processes (for all my modules) in top.

@Alphascrypt Yes exactly Fo you know how I can do this?

@Cato Hi!, The documentation for tests are living only in test source ;) This is something. We need to an better documentation.

Are you interested to do it? https://trello.com/c/UwqL27A3/29-add-documentation-of-testsuite

I’m not a very good at writing documentation.

But in short terms,

The tests are living in tests directory, there two kind of test, unit and e2e.

We are using mocha and spectron`, the last one is for the tests of e2e. For every e2e test is using a configuration file. When the test run load the configuration file and we check expected result of the MagicMirror instance in Electron mode.

You can using the follow sentences to run testsuite

Unit test: npm run test:unit E2e tests: npm run test:e2e Unit + e2e: npm test

If you can run especific test you need execute mocha from your path where is installed, in my case inside of MagicMirror directorio. Example of running the specific unit test for calendar functions.

NODE_ENV=test ./node_modules/mocha/bin/mocha tests/unit/functions/calendar_spec.js

Result:

Functions into modules/default/calendar/calendar.js capFirst ✓ for 'rodrigo' should return 'Rodrigo' ✓ for '123m' should return '123m' ✓ for 'magic mirror' should return 'Magic mirror' ✓ for ',a' should return ',a' ✓ for 'ñandú' should return 'Ñandú' shorten ✓ for ' String with whitespace at the beginning that needs trimming' should return 'String with whit…' ✓ for 'long string that needs shortening' should return 'long string that…' ✓ for 'short string' should return 'short string' ✓ for 'long string with no maxLength defined' should return 'long string with no maxLength defined' ✓ should return an empty string if shorten is called with a non-string ✓ should not shorten the string if shorten is called with a non-number maxLength ✓ should wrap the string instead of shorten it if shorten is called with wrapEvents = true (with maxLength defined as 20) ✓ should wrap the string instead of shorten it if shorten is called with wrapEvents = true (without maxLength defined, default 25) 13 passing (29ms)

If need something is not clear let me know.

@broberg : the requirement is not like that. The original idea is module internal timer with 1 second interval for example, can be replaced with event from the clock. The module no longer required to implement the timer itself.

@Jopyth exactly. Wich wouldn’t make much sense.

Starting from version 2.1.0 (currently the develop branch) the default modules will add the following functionality: Possibility to use the the calendar feed as the source for the weather (currentweather & weatherforecast) location data.

When the location and locationID are both not set, the location will be based on the information provided by the calendar module. The first upcoming event with location data will be used.

Since this feature is still in the develop branch, it’s not final and might change. Suggestions are welcome.

In version 2.1.0 (the current develop branche) the module and nodeHelper API both feature the requiresVersion variable. This allows you to set the minimum version number of the MagicMirror framework that is necessary for your module to run correctly. This is important, because version 2.1.0 will contain some API changes that might prevent your module from running in older versions.

More information about this feature can be found here: https://github.com/MichMich/MagicMirror/tree/develop/modules#requiresversion

Example code:

Module.register("testModule", { requiresVersion: "2.1.0", start: function() { // do something } });

Of course, this feature would be way more powerfull if it was available starting from version 2.0.0. Unfortunately I did not have the time yet to invent a time machine. Therefor you can use a workaround if you really must do some manual checking. Starting from version 2.1.0, the frontend javascript will have a global variable called version. This is a string that represents the current version of the MagicMirror. In the node helper, this string is available via global.version.

So, if absolutely necessary, you can use the following code in your module:

// main module if (!version) { // this is an old version, give the user a warning and don't perform any other new API calls. } // node helper if (!gobal.version) { // this is an old version, give the user a warning and don't perform any other new API calls. }

Since this feature is still in the develop branch, it’s not final and might change. Suggestions are welcome.