Forum QT

I'm trying to configure the qt creator 19.0.2 in order to develop mobile applications. So far, I've installed Android studio and then qt detected the new Android virtual device as Pixel 8 but on running an already present qt application, it is generating errors on building and running the application. The device and kit have been set as the device detected on Android Studio. The following are the screenshots attached for reference. It would be really helpful know from someone the mistake and the correct steps for the setting up qt creator for developing mobile applications and also to test the simulator and emulator on an already present qt application.

Hi, i am using CachyOS Linux, Arch based Installed qtcreator using: sudo pacman -S qtcreator Wanted to try using AI in my project I have a ChatGPT Plus plan Went to Settings > AI > ACP Servers Added the template Codex 1.13.1 There is a hint under the Template setting saying: npx @agentclientprotocol/codex-acp@1.13.1 When i click on Show Agentic AI Chat in Side Panel and i login or authenticate using the browser to chatgpt, i can chat normally BUT the AI can see and write to files outside my project dir Furthermore when i set the Mode to Ask For Approval it reverts back to Approve for me when i restart qtcreator This is dangerous, any idea how to fix that ? I want the AI to only access my project folder, i want to only ask it question, i don't want it to edit anything or see anything outside my project dir

Otherwise this thread might be relevant.

@f222 Glad I could help :) Don't understand the issue in your second paragraph so i will leave that with you. It was a guess about TZ. That is a normal environment variable under Linux (which I use) but not so much under Windows. There it gets complicated: it may depend on the compiler code you use (MinGW vs MSVC). I believe it is also used automatically by the C runtime code you link/dynamically load (DLLs) against. How that in turn relates to C++ runtime code I don't know. And I suspect Windows calls do not use it, only C/C++; and then I don't know which Qt calls' implementations use C/C++ functions versus Windows-SDK ones, and maybe a mixture (e.g. your time calculation calls use the C/C++ TZ variable but your name-of-timezone uses a Windows call?). And for all I know Qt's internal code may have changed in that area between your old-working Qt5 and new-non-working Qt6. It's all perhaps a minefield, suck it and see :)

We get a black window when running smallest possible Qt application using OpenGL on Linux with an Nvidia graphics card (proprietary 580.159.03). To rule out environment and driver problems, we have written three corresponding applications using xlib only, xcb only, and a xlib xcb mix. All three of them work on the same Nvidia graphics card in the same environment. The attached xlib.cpp, xcb.cpp, xcb_xlib.cpp and qt.cpp can be built following the instructions in build_and_run.sh (replace the QT path in the script to where your Qt installation is first). Replacing EGL_PLATFORM_XCB_KHR with EGL_PLATFORM_X11_KHR in xcb_xlib.cpp, and using xlib display, causes eglCreatePlatformWindowSurfaceEXT to return a nullptr for EGLSurface in xcb_xlib.cpp, exactly what we see in Qt. Is there something we're missing in qt.cpp to make this work or is this a bug in Qt that can be fixed? We started looking into the Qt source code, the call to eglCreatePlatformWindowSurfaceEXT(EGL_PLATFORM_X11_KHR, xlib display, [...]) returns 0. If we modify Qt to call eglCreatePlatformWindowSurfaceEXT(EGL_PLATFORM_XCB_KHR, xcb connection, [...]), we instead get a valid surface that can be queried with eglQuerySurface that report the correct size. The window is still black but having a surface is a good start for anyone looking into this. Attached source files

Pretty much what's in the title. I'm trying to use the new OpenAPI client generator from Qt, the API I'm trying to use is not tied to a particular server so I need to be able to set the server base url at runtime. I didn't find a way set it from generated openapi client (tested using Qt 6.11.2). the API documentation is very sparse maybe I missed something. A possible workaround I can think of would be to patch the openapi yaml to set a server with a template variable for the hostname.

We are happy to announce the release of Qt Creator 20.0.2! https://www.qt.io/blog/qt-creator-20.0.2-released

@taniya-mittal yes you can, this is an exemple https://github.com/jordanprog86/QML-Chalkboard.git

I filed this issue too: https://qt-project.atlassian.net/browse/QTBUG-150742 - a suggestion to add support for unix sockets in the SatelliteSource object, which would mean no need to pipe gnss-share output. I would really like for someone to confirm if the sattlitesInView list is empty - I have not been able to fix that, and I consider filing an issue for that as well.

For an educational project, I want to compile Qt 6 C# (presumably, via the new Qt Bridge) to GitLab Pages-compatible WASM (presumably, via Emscripten). Is this feasible, and/or possible? If not, I am happy to file an enhancement request for Qt Jira's QTBRIDGES product. Though, I fear that it may be as difficult as what github.com/pyodide/pyodide-recipes/issues/183 describes.

Sorry; I would have edited the post but the site does not allow me. The error message I posted was from when I had my custom debugging helpers on. Them being on or not (or even present) has no impact on this failure, but they do change the error message slightly and I didn't want to confuse the issue with that oversight. Here is a version of the error with no involvement from those: &"python theDumper.fetchVariables({\"allowinferiorcalls\":1,\"autoderef\":1,\"context\":\"\",\"displaystringlimit\":300,\"dyntype\":1,\"expanded\":{\"inspect\":100,\"local\":100,\"local.boxHigh\":100,\"return\":100,\"watch\":100},\"fancy\":0,\"formats\":{},\"nativemixed\":0,\"partialvar\":\"local.boxHigh\",\"passexceptions\":0,\"qobjectnames\":1,\"qtnamespace\":\"\",\"qtversion\":331539,\"resultvarname\":\"\",\"stringcutoff\":10000,\"timestamps\":0,\"token\":718,\"typeformats\":{},\"watchers\":[{\"exp\":\"6d446972656374696f6e\",\"iname\":\"watch.0\"}]})\n" >~"bridgemessage={msg=\"b' COULD NOT ACCESS FIELD: union {...}'\"},\n" >~"bridgemessage={msg=\"b' COULD NOT ACCESS FIELD: union {...}'\"},\n" >~"bridgemessage={msg=\"b' COULD NOT ACCESS FIELD: union {...}'\"},\n" >~"result={token=\"718\",data=[{iname=\"local.boxHigh\",name=\"boxHigh\",address=\"0x555555f48b78\",size=\"12\",numchild=\"1\",sortable=\"1\",children=[],type=\"glm::vec3&\",value=\"\",},{iname=\"watch.0\",wname=\"6D446972656374696F6E\",numchild=\"0\",type=\" \",value=\" \",},],typeinfo=[],partial=\"1\",runtime=\"0.012951968994457275\",

@rida_zouga OK :) Now that you are using the color just for the background and filling first you can drop the alpha/opacity, e.g. QColor(255, 255, 0) should be pure yellow. Mine was just for illustration.