Silly me I have been testing the new flag field by an bitwise
or instead of the proper & :-). Can't imagine how this did slip in...
Corrected patch attached.