In fact, I placed it there so that the construction is the same as that of ‹ Continue only if ›
But since you’ll know the second element is necessarily a letter, no problem, right?
I note here a few points that I plan to change in a v2 of these mockups :
- rename the action « Condition ‹ If… Then… Else… › » to « Conditional blocks ‹ If… Then… Else… › », because I think that’s more what we’re adding: blocks that execute according to a condition
- rename the button « Add a condition » to « New condition + », to be consistent with the « New action + » button
- apply the numbering 1.✓.
1 Like
Personally, I think it lacks color to clearly see the blocks. Otherwise, etc.
Hi @StephaneB !
Thanks for taking the time to look, that’s really nice 
A few questions/remarks:
- Is the « Condition "If… Then… Else…" » block that frames the 3 blocks really necessary? Couldn’t the « If… » block be the global container that itself contained the Then and Else blocks? That would reduce the level of encapsulation which is already very high; I think the simpler we make it, the better
- If I click on « Add a condition », what happens?
- Is it possible to add a temporal condition? A condition on a calendar event?
- How do you remove a condition?
- How do you add/remove a group of actions?
- For the numbering of the blocks, I think there’s already a missing level.
In your first example, the condition is already a « 1.1 », so if we add your « A.1 », it becomes « 1.1.A.1 ».
The « 1.✓.1 » I don’t really see the point of, I admit, it’s not very clear to mix text and an icon.. it’s also going to render horribly on Windows which has awful emoji 
In Whimsical, no color, or at least I didn’t find any… But it could be a good idea to add (a little) when it’s developed in Gladys.
Good point, I hadn’t studied that closely. Actually, today, among all the actions addable with the « New action + » button, 5 are actually conditions. And it’s a good thing that the If… Then… Else… can offer them all. I illustrated this in mockup v2
I really think so. It makes for a rigorous construction, with 3 sections If Then Else that are at the same level. Especially since by including all possible conditions, the « If… » needs to be clearly delimited
I hadn’t gone that far in the mockup, but yes of course we can remove conditions, or the entire conditional block, or each action or block in the « Then » and « Else » sections
Two remarks in passing:
- it’s odd that deleting an action is an ‹ X ›, while deleting a block is a trash can. It would be good to harmonize
- it’s odd that you can’t delete the 1st block in a scene. Any particular reason?
Uh, well no, I don’t see the point of numbering the If as 1.1, because there would never be a 1.2.
ok, noted. In mockup v2, to avoid using an A=Then and an S=Else which wouldn’t work in other languages, I proposed a V that looks like a checkmark validating for Then, and an X that looks like a cross rejecting for Else… What do you think?
So, mockup v2. La scène finale a changé un peu : un message s’affiche, et si il fait frais dans une des deux pièces et si c’est le matin et si ecowatt (ecowatt) est ok, alors le radiateur s’allume et un message le confirme 5 minutes après. Et
Step 1: an action already exists, we’re about to add an action « Conditional Blocks » in the same block
Step 2: The « Conditional Blocks » action has just been added; it is empty, including the « If… » section (unlike the v1 mockup)
Step 3: A click on « New condition » displays the condition which we choose among the 5 existing ones
Step 4: The complete scene, where you can see the conditions combining. I didn’t keep the specific title « Continue in the Then block… only if »
Final notes:
- For consistency with the other conditions, I think « Continue only if » should be renamed to « Condition on variables »
- When adding a new action, the dropdown is a bit messy. I think it deserves sorting (in particular to group the « Condition … » items, or the « Send… » ones)
Thanks for all your thoughts @StephaneB!
But is that really logical?
In programming, for example, the « If » is not on the same level as the « Then », but rather above it.
I’d be curious to see a proposal with the If placed directly at the level of the first block.
Indeed!
If it were deletable, you wouldn’t be able to add actions anymore 
The UI is translated, I don’t see the problem If we find it logical to use « A » for alors in French, we’ll use « T » for « Then » in English — it’s only the display anyway, right?
Good idea!
However, to be seen, but I think we’ll need to create a new action set to maintain backward compatibility! The actions currently in production must remain functional even after the update.
Why not!
Thanks @pierre-gilles, I’ll look into how the other placement of the If block works…
In the meantime, two other ideas occurred to me (complementary or not, I’m not sure…). What do you think? :
- if the Then and Else sections become a bit long, it could be handy to have a button to expand or collapse the content of each section
- in the title bar of the action ‹ Blocs conditionnels… ›, there could be 2 clickable links to jump to the start of the Then and Else sections
1 Like
[quote="StephaneB, post:51, topic:6223
@pierre-gilles, here is the variant (just for step 3 of my example) in which the « If… » is no longer in a section, but integrated at the start of the « Conditional blocks » action.
I also put the A/S back in the numbering (since it will be translated), added a collapse/expand icon, and something to navigate easily between ‹ If ›, ‹ Then › and ‹ Else ›, as well as a ‹ Next › that would send to the end of the ‹ Else ›.
I didn’t choose between the cross and the trash can for deleting a block or an action. I don’t know which you prefer for consistency… But I also think that’s not the purpose of this feature request 
Does that work for you, and shall I adjust the other steps?
Well, it seems to me that it’s actually the last one, the one that’s always empty of actions, that shouldn’t be deletable.
Today, if I take the example of a scene with 4 blocks, blocks 2 and 3 are deletable, but not blocks 1 and 4.
In my opinion, blocks 1, 2, and 3 should be deletable, and not the last block, no. 4. And when there’s only one block, it isn’t deletable (it is the last). And when there are two blocks, the first should be deletable (but not the last, no. 2).
And in each of these cases, you can still add actions in the last block, which is always visible and empty of actions.
Am I wrong in my reasoning? In the mockup above, I added a way to delete the 1st block…
What would be nice is to have a plus button between the action blocks like Zapier does
Here in the mockup, have a plus between action block 1 and action block 2.
For slightly long scenes, this would allow adding an action block anywhere in the scene.
1 Like
I like the idea but it’s a new feature. Let’s try to keep this one (already complex) as simple as possible.
Can you create another request?
Actually, it already exists
1 Like
I promise, I’m trying 
Yes, it’s a new feature
I hadn’t seen that the request already existed. I added my vote.
That looks good to me!
Just in terms of design, I think the « new condition + » button should be placed elsewhere; it doesn’t make much sense there.
For the « collapse » button, I think it’s better to do like I did in the MQTT integration:
You can use the cross; it’s lighter for this already quite busy interface!
Also, the « If / Then / Else / Next » links repeated on each line I find too cluttered…
Another point: the « Else » will not be used in 100% of cases, so in my opinion it should be something that is « collapsed » by default.
Yes, you’re right!
Ok, Pierre-Gilles, thanks for your feedback. I’ll incorporate that to redo the 4 complete mockups.
To harmonize the delete icon, it would therefore be an X everywhere, so the trash icon used to delete an action block would become an X. But do I include that in this enhancement request, or is it a separate one (because it’s not only for the block that will contain a « Conditional blocks » action)? I know you like each request to be very specific…
And likewise for making the first action block deletable, should I do it here, or is that a separate request? Or can it be added to the request [Scènes] Pouvoir insérer un bloc de scène (plutôt qu'un ajout en fin), because it’s quite similar?
You’re right, we can separate all these developments so we don’t mix everything