This Problem:
still occurs on PolyScope Release 5.3 using API 1.5.0 Did i miss something that must be changed through the new API 1.6.0 ?