Simple but helpfull: Add [rising/falling/changed] option for Case-Stuctures with a boolean-type case selector

[_EMG_]

Many times, at least in my codes, it's necessary to act only on a rising / falling or changed edge of a boolean signal.

Probably this option can be added for CASE-structures with a boolean-type case selector of cause. 

[d.w.b]

See https://www.vipm.io/package/openg.org_lib_openg_toolkit/ user.lib\_OpenG.lib\boolean\boolean.llb\Boolean Trigger__ogtk.vi

'This VI is used to detect rising and falling edges of the Boolean Input. "Rising Edge" is TRUE if Boolean Input is TRUE and was previously FALSE. "Falling Edge" is TRUE if Boolean Input is FALSE and was previously TRUE. This VI is intended to be used in loops to aid in user input polling.'

[_EMG_]

I know such VI's exist, I build my own FGV years ago. Anyway It would be nice to have such functionality like "Ignore upper and lower case" option at string selectors.

[wiebe@CARYA]

>Anyway It would be nice to have such functionality like "Ignore upper and lower case" option at string selectors.

Like the existing option Case Insensitive Match? 🙄

Or do you mean to have an option for Booleans like this option? It isn't clear...

Why restrict this just for Booleans? Numbers can be rising\falling\change... Even strings can be rising\falling\change.

I won't mind this, but I won't use it. It will (when used) add state to your code (a history, like FBN and uninitialized SR) which is (in my book) undesirable.