Ok Thiago, sorry for the wrong example. In fact I had several variables
like that, one of them a QObject. I left only the QMap in my example to
make it simple, I should has left only the other one.
Sorry for that again. Your answer was correct: this warning comes from
creating a QObject before
On 6 December 2016 at 13:27, Philip Schuchardt wrote:
> I've always wondered if you could put a QGraphicsScene in another process
> and then render to shared memory buffer QSharedMemory
> (https://doc.qt.io/qt-5/qtcore-ipc-sharedmemory-example.html). Then you
> could query the shared memory (as a
I've always wondered if you could put a QGraphicsScene in another process
and then render to shared memory buffer QSharedMemory (
https://doc.qt.io/qt-5/qtcore-ipc-sharedmemory-example.html). Then you
could query the shared memory (as a pixmap) in the main application. This
would get around the QGr
On 8 September 2016 at 18:29, Tomasz Siekierda wrote:
> On 8 September 2016 at 04:17, Ch'Gans wrote:
>>
>> Hi there,
>>
>> I'm currently working on a Gerber viewer (Gerber is an old file format
>> still widely used in the electronics PCB manufacturing industry,
>> dating as far back as the old ph
Em segunda-feira, 5 de dezembro de 2016, às 22:54:31 PST, maitai escreveu:
> I had my main like that:
> QMap folderMap;
> int main(int argc, char *argv[])
> {
> QApplication *app = new QApplication(argc, argv);
> .
> }
> and I had folderMap defined as external in other classes when needed
> Am 05.12.2016 um 22:54 schrieb maitai :
>
>
>
> I am just wondering why creating a 'simple' QMap (or QString, whatever) in
> the same main() forces qApp to be created in another thread.
Well of course it is not, but you create a Object before the QApplication
class. Your map is created bef
I had my main like that:
QMap folderMap;
int main(int argc, char *argv[])
{
QApplication *app = new QApplication(argc, argv);
.
}
and I had folderMap defined as external in other classes when needed
I was getting the warning in that case.
Now I have:
QMap *folderMap;
int main(int argc,
Em segunda-feira, 5 de dezembro de 2016, às 14:27:01 PST, maitai escreveu:
> Hello,
> Can you explain what is the bad thing about having this message?
It's a warning from Qt. That should be enough reason. ALL Qt warnings are bugs
in your application. You should develop with QT_FATAL_WARNINGS set
Sweet! Sounds interesting. I want to play around with combining QtLocation
(QML Map item), DEMs, and Qt3D to do some simple terrain modeling.
On Mon, Dec 5, 2016 at 1:59 PM Sean Harmer wrote:
> Hi,
>
> On 05/12/2016 18:54, Philip Schuchardt wrote:
> > I want to render QML to an OpenGL texture th
Hi,
On 05/12/2016 18:54, Philip Schuchardt wrote:
I want to render QML to an OpenGL texture through a framebuffer and then
share that texture with Qt3D.
there is a working WIP progress implementation of this on gerrit at:
https://codereview.qt-project.org/#/q/status:open+project:qt/qt3d+branc
Hi,
On 05/12/2016 17:59, Juan Jose Casafranca wrote:
Just for curiosity, why it is not typed as QCameraLens as that it is the
"real" camera?
Because QCameraLens is only responsible for the projection matrix part
of the overall transformation. It only cares about field of view, aspect
ratio e
I want to render QML to an OpenGL texture through a framebuffer and then
share that texture with Qt3D. Rendering to a framebuffer is fairly straight
forward with a
QQuickRenderControl. A good example of it is in
https://doc.qt.io/qt-5/qtquick-rendercontrol-example.html. Is there any way
to share Op
Just for curiosity, why it is not typed as QCameraLens as that it is the
"real" camera?
El 5 dic. 2016 6:34 PM, "Philip Schuchardt" escribió:
> Awesome, thanks!
> On Mon, Dec 5, 2016 at 12:32 PM Sean Harmer wrote:
>
>
>
> On 05/12/2016 16:37, Philip Schuchardt wrote:
> > Awesome! Thanks! I real
Ok, here's another one for the brain trust...
I'm creating windows in a tasktray application (Windows 7 64-bit). These
"child" windows inherit from QWidget and are not parented, but they are being
created by the main application.
I can "glue" them to the screen (i.e., top of Z order) using t
On 05/12/2016 16:37, Philip Schuchardt wrote:
Awesome! Thanks! I really like the entity and component system in qt3d!
It just takes time to understand all the components and how they play
together with each other.
Yeah, it's a little bit of a mental shift from traditional OOP but means
we ca
Awesome, thanks!
On Mon, Dec 5, 2016 at 12:32 PM Sean Harmer wrote:
On 05/12/2016 16:37, Philip Schuchardt wrote:
> Awesome! Thanks! I really like the entity and component system in qt3d!
> It just takes time to understand all the components and how they play
> together with each other.
Yeah,
2016-12-05 17:56 GMT+01:00 Gunnar Roth :
> Try to use this patch and tell me if it works for you
I'll do, but probably only in a few days. I'll keep you informed.
--
Software Engineer | Trimble Imaging Division
Rotebühlstraße 81 | 70178 Stuttgart | Germany
Office +49 711 22881 0 | Fax +49 7
This is a bug.
Try to use this patch and tell me if it works for you:
diff --git a/qmake/generators/win32/msvc_nmake.cpp b/qmake/generators/win32/msvc_nmake.cpp
index ae139c2..41bec4c 100644
--- a/qmake/generators/win32/msvc_nmake.cpp
+++ b/qmake/generators/win32/msvc_nmake.cpp
@@ -409,14 +409
I checked out Qt 5.6.2 from the git repository and configured it with
..\configure -prefix "%DESTINATION_DIR%" -release -force-debug-info [...]
Qt configures, builds and installs ok, but when using the result in a
project, I get this linker warning for every executable using Qt:
qtmain.lib(qtmai
Awesome! Thanks! I really like the entity and component system in qt3d! It
just takes time to understand all the components and how they play together
with each other. If I aggregate the QTransform and QCameraLens into my own
camera code, do I need to subclass framegraph node to select my custom
ca
On 12/5/2016 12:48 AM, Michael Sué wrote:
Hi,
with a enum class you'll need to give the type explicitly, as there is no
auto-conversion to int:
settings.setValue("report.stacking",
QVariant::fromValue(report_stacking));
The same with QVariant::value: var.value();
Thanks, Michael (and
> On 5 Dec 2016, at 14:32, Konstantin Tokarev wrote:
> 05.12.2016, 16:30, "Shawn Rutledge" :
>>> On 4 Dec 2016, at 18:17, Jason H wrote:
>>>
>>> I am trying a naive compile of Qt 5.7.0 (from source tarball) on a Pi zero
>>> (no cross compile) I've got all the dependencies installed and Jessi
05.12.2016, 16:30, "Shawn Rutledge" :
>> On 4 Dec 2016, at 18:17, Jason H wrote:
>>
>> I am trying a naive compile of Qt 5.7.0 (from source tarball) on a Pi zero
>> (no cross compile) I've got all the dependencies installed and Jessie is up
>> to date.
>> I keep running into GCC 4.9 compile
> On 4 Dec 2016, at 18:17, Jason H wrote:
>
> I am trying a naive compile of Qt 5.7.0 (from source tarball) on a Pi zero
> (no cross compile) I've got all the dependencies installed and Jessie is up
> to date.
> I keep running into GCC 4.9 compiler errors. Not that the Qt code is bad, but
> t
Hello,
Can you explain what is the bad thing about having this message?
BTW I had this message since a long time, since this thread I have
removed some global QObject declarations in my main, and the message is
gone. But it's not clear to me if it's any better and why.
Philippe.
Le 05-12-201
Hi,
We will have some recordings coming out soon – editing has taken some time.
Will post a message here when they are ready.
Best regards,
Carl Engh
From: Edward Sutton [mailto:edward.sut...@subsite.com]
Sent: 1. desember 2016 18:15
To: Carl Engh
Cc: interest@qt-project.org
Subject: Re: [Inte
Hi,
I see you found it already but I'll explain for posterity. All Qt 3D
wants from a "camera" is a view matrix and a projection matrix. These
come from the QTransform and QCameraLens components respectively, which
are aggregated by QCamera. QCamera itself is not special, it is just an
entity
27 matches
Mail list logo
