adp001 opened this issue on Dec 27, 2019 ยท 92 posts
adp001 posted Mon, 30 December 2019 at 11:18 AM
FVerbaas posted at 6:07PM Mon, 30 December 2019 - #4374983
adp001 posted at 4:27PM Mon, 30 December 2019 - #4374975
More import question is: Will they upgrade from QT4 to QT5?
I do not think MD will be doing that. I have the impression the Python API is not high on their list and they rely on development by an external party. I wrote the MD side bridgehead the way I wrote it, linking in one layer below the level they suggest, The level they suggest to use is/was plain buggy. I heard of no-one who used it with success.
Note that the API came with MD7 in fall 2017, yet they use Python 2.7. I do not see them changing unless they are requested by an important large client.
Changing from Python 2.7 to 3.x needs a lot of manpower.
And including QT5 in commercial software costs money. Maybe this is a point too.
QT5 supports allmost anything one needs for fast 3D display and computing.
Maybe a RPC-Interface QT5 <-> Poser could be something.
Complete new Poser interface based on QT5, right? You could propose this to Jenn. ;-)
No. Just a bridge to bring things in and out. But with a more direct binding (changes made in Poser are reflected directly over the bridge and vice versa). I started something like this years ago for C4D (very basic and for a special need).
I don't think Bondware has an interest in QT, because, as said: it cost money to implement it.