A restart is not enough; you need to recreate the container with the new image.
or that the machine running Gladys is great!
I had a Gladys Docker on my Synology DS918 with 16GB of RAM and lots of other Dockers running on it (but no large Docker containers) + a VM: in the end, my scenes were doing nonsense, notably my scenes for the washing machine which took between 2 and 5 hours between start and stop even though the machine ran for 30 minutes…
Since I switched to a mini PC with an i5-7600T (and now an i7-7600T 
), Gladys has never worked so well. But I guess I have some things that run too fast, particularly for cost calculation; I need to keep an eye on that.
Thanks to you for the improvements. I tested it and didn’t come across any issues.
The only thing is that the drag&drop of an action block doesn’t work from inside the If Then Else to the outside, or vice versa. But that might be intentional to avoid a malfunction… It does work well, however, between the Then section and the Else section. And individual actions can be moved anywhere; that’s fine
Hi @pierre-gilles, thanks for the fixes, it’s really great work!
Below are my comments:
The behavior is perfect: if I delete all deletable blocks (with the trash) only one remains, and if I delete all the actions of the penultimate block (the last one never having any action) then that block is automatically removed 
I reproduce the behavior: a Then (or Else) block cannot become a simple actions block outside an IfThenElse. It can go into another IfThenElse block at the same level (whatever the level, e.g. 22S1 to 23A2 or 22S12A1 to 21A13A1) BUT not into a block of a lower or higher level (23A2 to 22S12A1 or vice versa) and I think that’s why it also can’t go to an external block (so of a higher level).
I just tested and actually it’s the total number of actions, meaning you can have 2 blocks of 1 action each, and it will show 2 actions in the summary. I think this information is representative of what’s underneath.
And it works the same way when you have a sub-IfThenElse (with actions) inside a Then (or Else) block: if you collapse that Then (level 1), it takes the number of actions from its level AND from the sub-block (level 2). It’s really great!
Note: I can’t move an IfThenElse block to another actions block (from block 2 to block 3 for example).
Note: If I move the block containing an IfThenElse to another block (from 2 to 1), it works.
If I move a block with an action into the IfThenElse block (from 2 to 1), everything breaks and nothing is clickable anymore 
[quote="mutmut, post:
I think it’s more an issue with the display of the « Chat » view than a scene bug 
I’ll test it
I find that very abstract, not convinced!
It’s intentional; if I implemented a mixed behavior it would be unusable because it’s impossible to determine which level you want to drag & drop to.
Example: You have a « If… Then… Else » condition that itself contains a « If… Then… » condition; if I drag & drop into a group of actions in the deepest « Then », in practice I’m also inside an action block of the intermediate « Then », and of the root action block. The drag & drop sees that you’re going to drop onto 3 different action blocks…
I think there are solutions, like not making the entire block « droppable » but only a drop zone at the end of the block, but that seems a bit out of scope for this development…
Is this behavior a blocker for you?
If yes, we need to do a specification job on the drag & drop: what do we want? (In that case @StephaneB, it’ll be up to you to take over)
They are indeed 2 actions I count the actions inside the blocks. Counting action blocks is of little interest, I think.
That’s intentional too; you can’t replace a « classic » action with a « Si Alors Sinon » action and vice versa, for the same reasons you can’t move an action block from a lower level to a higher level.
The same solution is possible, but it’s a proper, separate reflection on the drag & drop behavior; I find it a bit out of scope… Anyway, tell me if this seems blocking for release.
Ok I’ll investigate, that’s not normal.
Ok for the explanation, it’s clear. And no, I don’t think that’s a blocker.
@mutmut Do you have more information about this bug? I can’t reproduce it
I’m giving my opinion quickly (sorry for not being more available), but consistency brings understanding.
If the terms change, it’s impossible to find your way around.
I think cleaner / more professional consistent texts are better than very (too?) simple texts with less consistency.
The user might not exactly understand what an action does just by reading its name, but once tried, they will understand and will look for the same terms everywhere.
And let’s be clear that Gladys users are not complete novices in IT either.
Personally, in my professional projects, if I’m afraid a button or an action isn’t clear enough, I add a detailed tooltip.
I find the proposal understandable, it’s plain French, not computer jargon there.
There, that was my tiny contribution to the debate
Thanks for all your work, guys!
and here it is:
I just tested on my end and I have an issue with drag & drop.
In the block’s conditions it’s not possible to add as a condition a Condition « If…Then…Else » block, that point is OK
The problem is that with drag & drop you can drag a Condition « If…Then…Else » block into the conditions of another Condition « If…Then…Else » block
For this I created a Condition « If…Then…Else » block in block 1 and another Condition « If…Then…Else » block in block 2.
I then drag & dropped the Condition « If…Then…Else » block from block 2 into the conditions of the Condition « If…Then…Else » block in block 1.
However the block is locked and we can’t do anything with it.
If I then move this block again and pull it out of the conditions it’s no longer possible to put it back.
Drag & drop works the first time but not the second. It should be blocked from the start.
Thanks @_Will_71 and @mutmut for your very thorough feedback, I managed to reproduce it quite easily thanks to your videos
It’s fixed!
A new Docker image is available:
gladysassistant/gladys:scene-if-then-else
[Tutorial: Run a test Docker image](Tutoriel: Lancer une image Docker de test
@pierre-gilles That’s OK with me
hello, successful test following your changes @pierre-gilles, no bugs.
This feature is available in Gladys Assistant 4.55 :
Thank you all for your valuable help, especially @StephaneB, @_Will_71, @mutmut and @hizo 