Note that there are some explanatory texts on larger screens.

plurals
  1. USBarbaris
    primarykey
    data
    text
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COWell, good question ... Everything that you develop in QML will work on all platforms supported by Qt including Win and Mac. The point is if you want a mobile and desktop app to work "natively" on the target platform, you need to change the UI - use desktop elements for desktop and mobile for mobile. So probably you will have to change it in your app as well. QML Desktop Widgets is something very experimental and in initial stage now according to Nokia. So I think it will be hard to make use of desktop elements such as table, push button, tab bar, etc with QML on desktop at this point.
      singulars
    2. COOk, then sorry but I haven't worked with Ogre3D. It is a 3D library for multiple desktop and mobile platforms and doesn't have a relation to the Qt tool set from Nokia. Although it might support Qt API but it doesn't mean its a part of Qt Framework. I'd suggest you to post this question in Ogre3D branch suggesting some standardized data interchange format (maybe a set of bytes) and asking how you can render that using Ogre3D.
      singulars
    3. COJust curious if his is Activity Monitor issue rather than Qt. Can you try to allocate a big chunk of data using any other class and see if Activity Monitor frees that memory ? Say: char* buf = new char[20971520]; delete [] buf; - that should be around 20Mb of memory and should be noticeable
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload