El Monday 07 December 2015, Ch'Gans escribió:
> Sorry to hijack the thread a bit, but I was thinking recently about
> adding contributor projects to some sort of CI.
>
> There's some nice Qt libraries around and some nice out-of-tree
> QtCreator plugins in the wild, wouldn't it be nice if such Ope
Hello Sean,
So I've implemented my simple camera controller. Before going into the
detailed text, here is how I set it up:
http://codepad.org/mXiL5Rs7
and then what I do in the controller itself:
http://codepad.org/9oARCaOv
The code is for testing, so please try to tolerate the stupid variable
na
A guinea pig now, am I? ;)
Am I assuming correctly that these new changes are available through the
5.6 HEAD? If so I'll fetch the repo and rebuild.
I think I understand what steps I need to take, so I'll try to implement my
controller and will report any *thoughts* ...
Thanks for the help!
Kind r
Nuno Santos wrote:
Hello Nunos,
Have you tried using a `ptr` that comes from another application? I think
that's
the context in which I get the crash.
I'll keep your code in mind though; the crash issue also reminded me that KF5
KWindowSystem doesn't yet have a plugin (backed) implemented fo
Rene,
I have recently dealt with creating content within a native window on mac given
a pointer. This was I got to:
QMacNativeWidget* IVstEditor::fromWindowRef(void *ptr)
{
NSView* view = (NSView*) ptr;
QMacNativeWidget *nativeWidget = new QMacNativeWidget(view);
nativeWidget->move
Thiago Macieira wrote:
> This is a crash inside the Cocoa plugin. Unfortunately, I can't read Objective
It is indeed...
> C++ code, so I have absolutely no clue what this line does or how it can even
> crash:
>
> [m_contentView removeFromSuperview];
Supposing that is indeed the crashing f
On Tuesday 08 December 2015 18:48:34 René J.V. Bertin wrote:
> Should QWidget::find(WId) return a non-null widget for any WId "owned" by an
> application
The docs say
"Creates a local representation of a window created by another process or by
using native libraries below Qt."
This is a crash i
Aha, a timely guinea pig :)
We've just merged in a bunch of changes to extend the Qt3DInput library.
Please take a look at:
http://code.qt.io/cgit/qt/qt3d.git/tree/examples/qt3d/simple-qml/CameraController.qml
for an example where we exercise the new API a little. We are in the
process of fo
Thiago Macieira wrote:
> On Tuesday 08 December 2015 17:14:46 René J.V. Bertin wrote:
>> Hello,
>>
>> I'm experiencing a crash in setMainWindow() with the code below (from
>> KF5-kwidgetsaddons). Is this something that is allowed on OS X, and
>> supposed to work?
>>
>> static QDialog *createWIdD
On Tuesday 08 December 2015 17:14:46 René J.V. Bertin wrote:
> Hello,
>
> I'm experiencing a crash in setMainWindow() with the code below (from
> KF5-kwidgetsaddons). Is this something that is allowed on OS X, and
> supposed to work?
>
> static QDialog *createWIdDialog(WId parent_id)
> {
> QW
Hello,
I'm experiencing a crash in setMainWindow() with the code below (from
KF5-kwidgetsaddons).
Is this something that is allowed on OS X, and supposed to work?
static QDialog *createWIdDialog(WId parent_id)
{
QWidget *parent = QWidget::find(parent_id);
QDialog *dialog = new QDialog(pa
Hello,
I wish to have the camera movement bound to a certain "slice" of the world
space. I didn't see that to be available through the default
implementation, so I assume I'd have to write my own component that
implements the input aspect and attach it to my camera. I've gone through
the sources, b
Thiago Macieira wrote:
> The culprit is plugin unloading coupled with QStringLiteral. I'm fixing Qt so
> that it doesn't unload plugins.
>
> See https://codereview.qt-project.org/140750.
OK, will have a look if that's a solution for 5.5 if I don't find a better one
(sounds more like a workaroun
13 matches
Mail list logo
