Possible bug, Battery Level block

[Ricardo Fernández Serrata]

If that block is set to proceed "When Changed" it proceeds immediately after the next BATTERY_CHANGED broadcast gets recieved, without checking if the level changed or not. This makes logical sense but it's "humanly unintuitive".

In order to make the block check if the battery level becomes different, it must be preceded by "is Battery Level" block (the same block, but proceeds Immediately) with an output variable that is used as input argument both for the min and max range of the "When Battery Level" block.

[Henrik "The Developer" Lindqvist]

Every "level" block works like that when no min/max level is specified, they all proceed when a new broadcast or whatever event is received, i.e. it's the OS that's incorrect cause an "change" event when the values hasn't actually changed.

I don't know if changing it now would be possible, without breaking every flow.

[Ricardo Fernández Serrata]

Thanks for the clarification. Changing it would probably break some flows, it's better to leave it untouched

[Horst Boss]

Ok, this is a bit old, but I just stumbled over it... =)

Couldn't you add an alternative block or just add an option to check, to let the user define which way he/she prefers?

That way old blocks stay the way they are and new ones could have the setting enabled?

[Henrik "The Developer" Lindqvist]

Sure, but implementing such an option for every block with an proceed When changed would be a huge undertaking.