Am 10.03.16 um 20:33 schrieb Hans Hagen:
indeed, this is a known issue and it's on my list to look into that (one can check for the location, at least that's what i do as a way out for now); we probably need an additional callback but not for the next release (as one might need to adapt code due to a break in compatibility)
ok good, so much the better if it is already known. yeah one can program around it, even though it is again a bit painful :-)
thanks frank
