Sorry, Zachary, et al. I hit "Send" a little to soon. I don't have any ideas for the keyboard event problem you mentioned. I use an in-house manipulater with keyboard/mouse interaction. The "paintEngine" fix I refer to will probably only work on your blinking/blank/refresh problem (again, if it works at all for Ubuntu).
Double check documentation for Qt events and OSG's interaction with them. That's my best advice... Sorry I couldn't be more help with this part... D.J. On Wed, May 26, 2010 at 4:35 PM, D.J. Caldwell <[email protected]> wrote: > Hello, Zachary. > > I use cow.osg for most of my testing. It may not be the most > intensive geometry, but it seems to work for testing simple behaviors. > > Try searching the OSG archives for "paintEngine". You should find a > fix that MIGHT help with what you're seeing. Under Microsoft Windows, > there appears to be a refresh problem requiring the paintEngine tweak. > I don't know what impact it may have for Ubuntu. > > AdapterWidget versus QOSGWidget: I could be wrong, but I believe using > AdapterWidget restricts osgViewer to single threaded mode, whereas > QOSGWidget is supposed to allow single OR multithreaded modes. > > I hope this helps... > > D.J. > > On Wed, May 26, 2010 at 3:29 PM, Zachary Hilbun <[email protected]> wrote: >> Hi, >> >> I'm using Eclipse with the Qt plugin in order to develop c++ osg code under >> Ubuntu. I've compiled and run the osgviewQT example and have the following >> questions. >> >> The example does not fully work. I'm using the OSG cow as a test model. >> Is this example the preferred way to use osg under Qt? If it is not, I'll >> abandon it and use whatever better way is available. If it is, I need the >> following questions answered. >> >> Using QOSGWidget and --CompositeViewer, the OSG cow flashes briefly and then >> there is an empty screen. >> >> If I use QOSGWidget as the widget using all 3 modes (--CompositeViewer, >> --MTCompositeViewer, and single), it does not respond to the keyboard keys >> for w, t, l, b, s, h. It looks to me like setupManipulatorAndHandler uses >> addEventHandler to handle keyboard events, but the only key that is >> responded to is the f key. The f key only moves the window around on the >> screen but does not make it full screen. I can see functions like >> keyPressEvent being called so that part is at least working. >> >> Only --MTCompositeViewer will respond to mouse input using the >> TrackballManipulator. This appears to be setup for all modes but does not >> work for the single view. >> >> If I use AdapterWidget as the widget, it responds to the mouse for >> TrackballManipulator in all modes (--CompositeViewer, --mdi, and single), >> but the keyboard does not work. The code does not appear to be setup for >> keyboard input the way QOSGWidget is. Is keyboard input not possible with >> AdapterWidget? >> >> Is there a reason for choosing to use QOSGWidget vs. AdapterWidget? >> >> Thank you! >> >> Cheers, >> Zachary >> >> ------------------ >> Read this topic online here: >> http://forum.openscenegraph.org/viewtopic.php?p=28257#28257 >> >> >> >> >> >> _______________________________________________ >> osg-users mailing list >> [email protected] >> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org >> > _______________________________________________ osg-users mailing list [email protected] http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
