Yes, you're right. The problem is already fixed in the nightly build, but 
not in the  Current version: 2.0.3 (2012-08-30 21:45:50) stable  available 
in the download page.

thank you,
Nico

-- 



Reply via email to