@Lino77 Thank you very much for reporting this, I am looking into it.

PS: That error was caused by an undocumented change in the object model. I've got a fix ready for v3.5-rc.2. Version 3.4.6 should not be affected.