Closed Snille closed 3 years ago
@Snille - thanks for the pull request (and also for providing a solution for #29).
The module files have changed somewhat recently. As a result the pull request has conflicts. Can you review the pull request to resolve the conflicts then resubmit so I can review?
Thanks
Hi @ianperrin, I'll see if I can figure it out. :)
Explanation: If "uselock" is set to "false", the scheduler does not lock the hidden modules.
Let’s say you have "Joe’s" profile that don’t show the clock. But Joe’s profile should only be shown between 07:00 to 15:00 on Mon-Fri or with Facial-Recognition or with MMM-TouchNavigation.
Then you have "Jane’s" profile that should show the clock but her profile is usually activated with Facial-Recognition or MMM-TouchNavigation.
So to show Joe’s profile at the correct times, you would schedule a group like this: global_schedule: [ // Show modules with the class "Joe" at 07:00 and hide at 15:00 on Mondays to Fridays. {from: '0 7 MON,TUE,WED,THU,FRI', to: '0 15 MON,TUE,WED,THU,FRI', groupClass: 'Joe'}
On the clock module you would set the class “Jane” and “Joe”.
The problem is, that when the Scheduler hides the clock, because Joe’s profile should not show the clock. Jane will not be able to see the clock either at those times, because the clock is “locked” by the Scheduler.
But, if you don’t set the “lock-string” with the scheduler, the clock module CAN be shown by Jane (another module).
I hope this makes sense. :)