I see - fixed in version 1.3.5 !!!!!

I use 1.3.4 --- so it will not be fixed in this version .... Ok.

My mistake - I mixed it up, thought 1.3.3.5 ....


Reply via email to