Hi Werner,
On Tue, 11 Sep 2018 at 12:02, Werner Modenbach
wrote:
> My integration is dated April 2013 and I didn't need any changes since then.
It might not have any issues with the usage case you have, but it
doesn't necessarily mean that it will work with all usage cases.
One area that broke
Hi Werner,
We share the same belief around Qt.
Concerning your implementation, it's not clear how you integrate the OpenGL
window into Qt. If you are willing to share a simple application that
demonstrates your setup that would be a nice start to understand and
discuss your approach ?
Recent
Hi Mathieu,
thanks for your support for OSG/Qt integration. I think there are really
many people using OSG together with Qt.
Qt is just great for building multi environment user interfaces.
But there is one thing I don't really understand. There is some
discussion sometimes about difficulties in
Mathieu MARACHE writes:
> Back from holidays...
>
> Community support is thin when considering OpenSceneGraph with Qt. I
> am currenlty the only maintainer of osgQt because I have a software
> using it and I didn't want the project to be tossed out.
>
> The Qt4 way of doing things with legacy
Back from holidays...
Community support is thin when considering OpenSceneGraph with Qt. I am
currenlty the only maintainer of osgQt because I have a software using it
and I didn't want the project to be tossed out.
The Qt4 way of doing things with legacy osgQt (that was droped from
On Mon, 30 Jul 2018 at 15:59, Andrew Cunningham wrote:
>
> Back on the original topic :)
>
> This is a really simple QtOSGWidget that I used as a starting point for an
> OSG widget in a QDialog. Simple and works fine.
>
> https://github.com/vicrucann/QtOSG-hello
Just had a quick look at the
Back on the original topic :)
This is a really simple QtOSGWidget that I used as a starting point for an OSG
widget in a QDialog. Simple and works fine.
https://github.com/vicrucann/QtOSG-hello
--
Read this topic online here:
On Mon, 30 Jul 2018 at 11:00, Wojciech Lewandowski
wrote:
> I find your response as rather harsh and wonder why it hits me. Thats why I
> feel the need to reply.
My response is blunt because I'm frustrated that despite my best
efforts to community clearly to the community and asking
Hi, Robert
I find your response as rather harsh and wonder why it hits me. Thats why I
feel the need to reply.
Sigh So it's good you guys are getting somewhere.
Sorry, we don't use 3.6 yet and haven't seen this announcement. And I am
glad its fixed in 3.6 already. Its a pity I doubled your
Hi Wojtek,
On Mon, 30 Jul 2018 at 08:53, Wojciech Lewandowski
wrote:
> I understand my setDrawBuffer / setReadBuffer observation was probably not
> the only problem. But I believe this one is genuine problem that should not
> be neglected. So I decide to write this small followup and elaborate
Hi Stuart,
I understand my setDrawBuffer / setReadBuffer observation was probably not
the only problem. But I believe this one is genuine problem that should not
be neglected. So I decide to write this small followup and elaborate a bit
to make it clearer. In the meantime I did some more research
Circling back to my original issue, I got my OSG Qt viewer widget running with
OSG 3.6.2 and osgQt by moving all the GL-related boilerplate after the main
window show() call happens. I'm not sure what changed in Qt or osgQt to require
this but this could be useful for other osgQt users.
Hi Joshua,
I fully agree with you. We are developing commercial software and started with
plenty of years ago. About 10 years ago we started to use osg and embedded osg
view into a qt widget based on the osg-qt project at that time. It worked
smoothly since then. Now we are on the latest
Hi,
I have just investigated the issue with OSG view set in QT window and
osgEarth REX engine which resulted in completely black screen. This was
probably different problem, but it sounds bit like yours so I decided I
will share my observations. Maybe it will help someone. What I found to be
an
?!?! gmail just sent the email mid sentence
> That exactly the same can be said for the OSG. Doesn't mean
Mean't to say:
On Sat, 28 Jul 2018 at 10:20, Robert Osfield wrote:
> > Now, there are huge firms that adopted Qt for decades and run multi billion
> > dollars systems on it.
The
On Fri, 27 Jul 2018 at 18:19, Joshua Tree wrote:
>
> I have to chip in here. Qt is the most reliable, industry standard UI for
> C++, period. In part this success is due to the moc autogeneration, which
> could get you out of SFINAE madness.
>
> Now, there are huge firms that adopted Qt for
I have to chip in here. Qt is the most reliable, industry standard UI for C++,
period. In part this success is due to the moc autogeneration, which could get
you out of SFINAE madness.
Now, there are huge firms that adopted Qt for decades and run multi billion
dollars systems on it.
That
Hi Andrew,
On Fri, 27 Jul 2018 at 17:14, Andrew Cunningham wrote:
> I would agree QT is not perfect but on the flip-side
> - It is the 'last man standing' of x-platform UI's.
This is down to the weakness of the alternatives rather as much as the
strength of Qt.
> - It's actively developed
robertosfield wrote:
>
> Personally I think Qt is broken in a number of ways. It's really time
> that the computer industry had a C++11 based cross platform Windowing
> API so we can all dump Qt,
>
I would agree QT is not perfect but on the flip-side
- It is the 'last man standing' of
On Thu, 26 Jul 2018 at 22:34, Stuart Mentzer wrote:
>
> Hi Andrew,
>
> I had no luck despite trying many variations. I had to put this work aside
> for a while with the plan to circle back and check for osgQt updates now and
> then. But if someone adds some ideas here I'll try them.
>
>
> To
Hi Andrew,
I had no luck despite trying many variations. I had to put this work aside for
a while with the plan to circle back and check for osgQt updates now and then.
But if someone adds some ideas here I'll try them.
To be honest I'm experimenting with Qt3D (feels a little dirty ;-). I
Hi Stuart,
If you resolve this please let us know. As a data point , I had a lot of
trouble with OSG 3.4.1 and QT 5.7 and the "black" window problem. I only
resolved it with some experimentation and I am still not sure why it worked.
Andrew
--
Read this topic online here:
Thanks for the outline. I will work through this and experiment with my code.
If I learn anything interesting/useful I'll post it.
Cheers,
Stuart
--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=74360#74360
I'm no code guru (more like a hacker), but I'll post what I do if it makes
sense and helps. Had to hand-type this as my code is on a different PC and I
couldnt copy. You'll probably see some typos and short cuts.
My setup is in a class called OSGDataViewer which double inherits a view base
Hi Robert,
Yes, I'm aware of the examples and osgQtWidgets runs fine with my builds. But
none of them match how we have used osgQt in the past with a single-view class
derived from osgQt::GLWidget and osgViewer and a GraphicsWindowQt. And there
are no examples for the new osgQOpenGL approach.
Hi Stuart,
On Tue, 17 Jul 2018 at 23:14, Stuart Mentzer wrote:
> Thanks for the info @davisjamesf. I wish I knew what secret sauce was needed
> to get this running. I'll keep trying and maybe I'll have luck with some
> future osgQt release.
>
> If you or anyone have some example code for a
Thanks for the info @davisjamesf. I wish I knew what secret sauce was needed to
get this running. I'll keep trying and maybe I'll have luck with some future
osgQt release.
If you or anyone have some example code for a single view class derived from
osgQt::GLWidget and osgViewer (or a better
This is probably nothing more than a data point of things working, but I had no
issue compiling/running OSG 3.6.2 and osgQt (qt 5.10 on windows 10 using VS
2017) and Linux (Cent OS7 / gcc 4.8.5).
--
Read this topic online here:
Hi,
I'm looking for info on the status of osgQt for OSG 3.6.2.
I tried using the osgQt git master code with my OSG 3.6.2 + Qt 5.11.1 Windows
build but I get a black OSG widget with our application, which works fine with
OSG 3.4.1. I tried a number of variations with no luck. I also tried the
29 matches
Mail list logo
