Skip to content
  • 143k Topics
    718k Posts
    V
    Hi, I am pretty new to QML development so bear with me. Versions: Python 3.13.5 Pyside 6.9.1 QtQuick3D Installed with pip Platform: Windows11 Running the main Python program from terminal, but got the same issue running in QT creator 16.02. I am trying to implement a pickable sphere into my application (for changing camera focus between objects on klick). But I have so far run into a couple of problems working with spheres. First I tried using the built in #Sphere source: Model { id: test_sphere pickable: true property real a: 6378.137 property real b: 6356.752314245 source: "#Sphere" position: Qt.vector3d(0, 0, -13000) scale: Qt.vector3d(100, 100, 100) materials: PrincipledMaterial { metalness: 0 roughness: 1 specularAmount: 0 emissiveFactor: Qt.vector3d(1, 1, 1) } } This model loads and picking works as excpected. The problem is that I couldn't find how the scaling factor works. Idealy I would like to set the radius/diameter of the sphere directly which would make the scaling easy. In the example using scale: Qt.vector3d(100, 100, 100) seems to just scale the sphere to an arbetrary size and I can't see how the numbers correspond to the envirenoment coordinates. I was not able to find any documentation on this either. So searching for alternatives I found that I could define the sphere with geometry: geometry: SphereGeometry { radius: 1.0 } This made scaling the sphere easy to work with, but when I set pickable to true, the program crashes when trying to load the sphere with error: Windows fatal exception: access violation So seems that there is something deeper in the QML/C++ not working. Code: Model { id: test_sphere pickable: true position: Qt.vector3d(0, 0, -13000) geometry: SphereGeometry { radius: 1.0 } scale: Qt.vector3d(100, 100, 100) materials: PrincipledMaterial { metalness: 0 roughness: 1 specularAmount: 0 emissiveFactor: Qt.vector3d(1, 1, 1) } } Is this a bug or is pickable simply not compatible when using geometry? Alternatively if someone could explane to me the scaling factor of the built in #Sphere that would be great!
  • Jobs, project showcases, announcements - anything that isn't directly development
    4k 23k
    4k Topics
    23k Posts
    Christian EhrlicherC
    So since it's a compiler bug - what should Qt do against it?
  • Everything related to designing and design tools

    129 389
    129 Topics
    389 Posts
    osirisgothraO
    I have a pretty decent setup for development I notice that QT design studio eats resources like candy -- even if my PC can keep up with it, the fans all kick up into high gear as if I had just accepted 30 network rendering jobs. Its only in the studio though, application performance itself is fine, and in QtCreator/Designer things are fine, just that monster seems to eat and eat, I am not surprised at all to hear people with setups under and at mid-end find it completely unusable. Maybe it has something to do with latest trends showing that environments like Unity can prove new developers really will just upgrade and upgrade and not bat an eyelash, carbon emissions be darned we need more games over here! :3
  • Everything related to the QA Tools

    79 215
    79 Topics
    215 Posts
    M
    I have a desktop app which runs on linux. I have my own laptop which runs on windows. I downloaded squish for windows on my own computer. I downloaded vncserver(tigervnc) on desktop app. Hoping to reach to my desktop app via using VNC on squish IDE and record scenarios. On my computer I created test suite, selected VNC as GUI toolkit. I did my configuration as needed under "Server Settings > Manage AUTs > Attacable AUTs". After that created test case and hit record button but got this error lines. "Warning: AUT '__squish__vncaut' (with AUT path '') does not exist FATAL Starting application Application '__squish__vncaut' could not be started. Squish couldn't start the AUT because the program doesn't exist. Make sure the AUT is really built and was not removed. Also make sure that the path to the AUT is correct in the settings. END End of test Giving up after error" I'm sure my vnc server runs on my desktop app. In https://forum.qt.io/topic/155170 i get that we might have similar issue. Should i download squish for qt? Or should i just download squishserver on my desktop app and expect it to be resolved? If i should download squish server on my desktop where can I the server package without downloading whole installation package on the application?
  • Everything related to learning Qt.

    386 2k
    386 Topics
    2k Posts
    Ash_QtA
    Hey there! You can return to the course in the catalog and relaunch it. Are you experiencing issues with this?
  • 2k Topics
    13k Posts
    Kent-DorfmanK
    I do a lot of python/pyqt database access using psycopg2 for PostgreSQL. It's so much easier to prototype these kinds of ideas in a language like python, and if needed then port it to c++, but truth be told, most of the time the python app is just works as is so no need to rewrite in c++. For something as simple as you are alluding to, the hard core OO models using DAO/DTO are probably overkill. Also, when dealing qith SQL queries it's "nice" to work in a language that is NOT strongly typed. Sorry if this is a round-about way to respond. Your path has merit in the realm of intellectual curiosity, but if you want it done quickly then python is a better option, and you can still wrap it in a Qt GUI. Yikes! Didn't notice OP was 9 months ago...
  • 4k Topics
    18k Posts
    Q
    具体操作步骤是这样的 第一步:下载QT源码(5.12.5),并解压 第二步:通过rsync传输目标机的sysroot 第三步:进入源码目录,配置configure文件 第四步:进入源码目录,进入qtbase目录,进入mkespcs目录,进入linux-aarch64-gnu-g++目录,修改qmake.conf: 第五步:运行脚本,然后出现提示 ’make’ 第六步:编译 当qmake.conf改成下面这样的时候,configure都无法完成 [image: 99807b2b-90a4-4aba-9cc4-ad01fa5782a6.png] 用原本的qmake.conf就可以配置成功 [image: 8d116342-bc0a-4b7a-a0ae-e2d88042fafa.png] 最后编译报错: gnu-g++ -o .obj/moc_qmlpreviewfilesystemwatcher.o .moc/moc_qmlpreviewfilesystemwatcher.cpp /usr/lib/gcc-cross/aarch64-linux-gnu/9/../../../../aarch64-linux-gnu/bin/ld: /home/hambes/qt-aarch64-build/qt-everywhere-src-5.15.2/qtbase/lib/libQt5Core.so: undefined reference to dlerror@GLIBC_2.17' /usr/lib/gcc-cross/aarch64-linux-gnu/9/../../../../aarch64-linux-gnu/bin/ld: /home/hambes/qt-aarch64-build/qt-everywhere-src-5.15.2/qtbase/lib/libQt5Core.so: undefined reference to dlsym@GLIBC_2.17' /usr/lib/gcc-cross/aarch64-linux-gnu/9/../../../../aarch64-linux-gnu/bin/ld: /home/hambes/qt-aarch64-build/qt-everywhere-src-5.15.2/qtbase/lib/libQt5Core.so: undefined reference to dladdr@GLIBC_2.17' /usr/lib/gcc-cross/aarch64-linux-gnu/9/../../../../aarch64-linux-gnu/bin/ld: /home/hambes/qt-aarch64-build/qt-everywhere-src-5.15.2/qtbase/lib/libQt5Core.so: undefined reference to dlclose@GLIBC_2.17' /usr/lib/gcc-cross/aarch64-linux-gnu/9/../../../../aarch64-linux-gnu/bin/ld: /home/hambes/qt-aarch64-build/qt-everywhere-src-5.15.2/qtbase/lib/libQt5Core.so: undefined reference to `dlopen@GLIBC_2.17' collect2: error: ld returned 1 exit status make[3]: *** [Makefile:119:../../bin/qmltestrunner] 错误 1 make[3]: 离开目录“/home/hambes/qt-aarch64-build/qt-everywhere-src-5.15.2/qtdeclarative/tools/qmltestrunner” make[2]: *** [Makefile:359:sub-qmltestrunner-make_first] 错误 2 make[2]: *** 正在等待未完成的任务.... 兄弟们,我哪里搞错了😭😭😭😭
  • This is where all the posts related to the Qt web services go. Including severe sillyness.
    1k 10k
    1k Topics
    10k Posts
    Axel SpoerlA
    Thanks for the hint. I have updated the post and corrected the link.