I recommend the slot to be a rounded rectangle, and "true" and "false" will be replaced with "on" and "off"
Can you explain more?
What are "unevaluated input textures"?
basically how the unevaluated inputs look
Unevaluated inputs are specifically made to look the same as regular inputs, because the user using the block does not need to know if it's unevaluated or not.
For example, the wait until block has an unevaluated input, but it looks like a regular boolean input. The user does not need to know that it's unevaluated, they just need to know what type of data goes into the slot.
Also, you seem to have Boolean inputs specifically in mind. Maybe you should give some context for why you're asking for this.
The developers have always wanted the difference between an evaluated and evaluated input to be seamless.
If I can't change the unevaluated textures, I want to have a new slot that signifies enabling something, rather than a condition. It could be a checkmark, a switch, whatever.
I must not be understanding you, because you seem to me to be using "unevaluated" to mean "Boolean." Can you show a picture of what you want?
Here are some designs.
Details
Design 1: Checkmark. Based on blockly. This could work. The 'false' was a copypasted character.
Design 2: Able switch. Yes, I know the design looks bad. Dont judge a book by it's cover.
Design 3: Squares. I was running out of ideas. I know it looks too mch like a color input
What @bh was asking, is why do you want this? Why is it so important to you that unevaluated inputs are changed?
so people can tell if an input is unevaluated, like you replaced the space with a red dot.
About the Any (Unevaluated) slot, its also a rounded rectangle.
I actually want new slots:
- Costume (Specific)
- Sound (Specific)
- Point (x and y)
- Pin (For librarys)
- Grid (For microbit)
- ID (Restrict certain chars)
Why would people need to know it's unevaluated? The reason they look the same as normal inputs, is because users shouldn't need to know if an input is unevaluated or not.
if you cant change the slots, can you add more inputs?
Could one of you please explain to me what this has to do with being unevaluated? As opposed to Boolean? If you're going to put a constant value in that slot, it doesn't matter when it's evaluated.
Is it that you're anticipating flipping the switch while the block is running?
On the growing list of things I want to do that Jens doesn't agree with is to replace the two Unevaluated types with a checkbox that could be applied to any type, so you could have Number (Unevaluated) or List (Unevaluated) etc. We really wanted List (Unevaluated) for the streams library.
About adding new shapes for input types, the trouble is that people have to learn what they all mean. The specific shape for numbers is needed because you can type directly into that slot, and you're limited in what characters you use. (Yes I saw your last example.) But most types you have to put a block into, and the blocks are all ovals except for predicates, so next you're going to want us to change block shapes, e.g., ⦚⊏⊐⦚ (that's the closest I could get in Unicode to a block with zigzag edges) for lists. And I think that would be needlessly intimidating for beginners, and hard to remember which is which.
Yeah, I feel like these would be very useful. I have had cases where one of these would have more sense than ANY (UNEVALUATED) which is what I had to resort to.
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.