Re: [osg-users] StateAttributeCallback marked deprecated

2016-02-09 Thread Judson Weissert
Thanks Robert! -- Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=66246#66246 ___ osg-users mailing list osg-users@lists.openscenegraph.org

Re: [osg-users] StateAttributeCallback marked deprecated

2016-02-08 Thread Judson Weissert
Bump. Why is osg::StateAttributeCallback marked deprecated? Thanks, Judson -- Read this topic online here: http://forum.openscenegraph.org/viewtopic.php?p=66239#66239 ___ osg-users mailing list osg-users@lists.openscenegraph.org

[osg-users] StateAttributeCallback marked deprecated

2015-12-08 Thread Judson Weissert
Hi, I was working with the master branch code from the GitHub repository (up-to-date as of today), and I noticed that osg::StateAttributeCallback is marked deprecated. (Perhaps it has been deprecated for some time now.) My question is: What is it supposed to be replaced with? Specifically, the

[osg-users] [osgPlugins] Indentation problem, OutputIterator::isEndl() no longer works after upgrading to Microsoft VC12 toolchain

2015-02-18 Thread Judson Weissert
Hello, I was recently working on upgrading compilers from VC10 to VC12, and came across the following regression when exporting *.osgt files. VC10: osg::Group { UniqueID 1 Children 5 { osg::Group { UniqueID 2 Children 3 { osg::Switch { UniqueID 3

Re: [osg-users] OSG deployment on Windows

2014-09-25 Thread Judson Weissert
Hi Émeric On 9/24/2014 1:03 PM, Émeric MASCHINO wrote: Hi, What's the best practice regarding OSG deployment on Windows? Indeed, several plug-ins depend on external libraries. Is it best to put the required DLLs in OSG_ROOT\bin\osgPlugins-X.Y.Z or rather in OSG_ROOT\bin, thus ensuring that

Re: [osg-users] Use of ref_ptr

2014-07-23 Thread Judson Weissert
Hi Norm, root-addDrawable (shape1); and root-addDrawable(shape1.get ()); are equivalent. The bare shape1 argument will be implicitly converted to Drawable *. http://trac.openscenegraph.org/documentation/OpenSceneGraphReferenceDocs/a00319.html The osg::Referenced objects store their own

Re: [osg-users] [osgText::GlyphTexture] Is GlyphTexture::resizeGLObjectBuffers missing a lock?

2014-06-05 Thread Judson Weissert
Hi Robert, On 6/5/2014 3:29 AM, Robert Osfield wrote: HI Judson, The design of osgViewer provides CompositeViewer for managing applications with multiple Views. Why are you using multiple Viewers? ComposisteVIewer has the ability to coordinate between multiple contexts that using multiple

Re: [osg-users] [osgText::GlyphTexture] Is GlyphTexture::resizeGLObjectBuffers missing a lock?

2014-06-05 Thread Judson Weissert
Hi Robert, On 6/5/2014 11:01 AM, Robert Osfield wrote: Hi Judson, On 5 June 2014 14:44, Judson Weissert jud...@mfrac.com wrote: If I have 3 distinct rootnodes (one assigned to each viewer, and each allocated separately), does calling resizeGLObjectBuffers() on one affect all of them? I

Re: [osg-users] OSG save scene to an image file

2014-03-04 Thread Judson Weissert
Hi Aviral, On 2/28/2014 4:36 AM, Aviral Goel wrote: But the callback doesn't get executed. I have 2 questions - 1) what am I doing wrong 2) Is this the preferred way to get the snapshot of the scene You may want to look at osgViewer::ScreenCaptureHandler available in the

Re: [osg-users] Please test svn/trunk and OSG-3.2 branch in prep for 3.3.1 dev release and OSG-3.2rc2

2014-01-27 Thread Judson Weissert
Robert, I performed an svn up from http://svn.openscenegraph.org/osg/OpenSceneGraph/trunk this morning, and the last revision is r14057 from 2014-01-24. Thus, I am not seeing your latest revision(s) mentioned below. I am not sure what the problem is at the moment. Regards, Judson On

Re: [osg-users] Please test svn/trunk and OSG-3.2 branch in prep for 3.3.1 dev release and OSG-3.2rc2

2014-01-27 Thread Judson Weissert
Hi Robert, On 1/27/2014 10:45 AM, Robert Osfield wrote: Hi Judson, On 27 January 2014 14:57, Judson Weissert jud...@mfrac.com mailto:jud...@mfrac.com wrote: I performed an svn up from http://svn.openscenegraph.org/osg/OpenSceneGraph/trunk this morning, and the last revision

Re: [osg-users] Please test svn/trunk and OSG-3.2 branch in prep for 3.3.1 dev release and OSG-3.2rc2

2014-01-24 Thread Judson Weissert
Hi Robert, Here are the interesting results for OSG r14046 trunk compiled in Visual Studio 2013: snip 30..\..\..\..\src\osgPlugins\dxf\dxfEntity.cpp(185): error C3861: 'min': identifier not found 30..\..\..\..\src\osgPlugins\dxf\dxfEntity.cpp(191): error C3861: 'min': identifier not found

Re: [osg-users] Please test svn/trunk and OSG-3.2 branch in prep for 3.3.1 dev release and OSG-3.2rc2

2014-01-24 Thread Judson Weissert
Hi Robert, Now down to: 3 Creating library E:/work/attic/OpenSceneGraph/build/lib/osgViewerd.lib and object E:/work/attic/OpenSceneGraph/build/lib/osgViewerd.exp 3GraphicsWindowWin32.obj : error LNK2001: unresolved external symbol protected: virtual void __cdecl

[osg-users] Compiling in MSVC with OSG_DISABLE_MSVC_WARNINGS defined causes warnings in user code to remain disabled

2014-01-08 Thread Judson Weissert
Hi, I recently noticed that some of the source files in my project were compiling, but were not generating some expected warnings. I believe I have tracked the problem back to a number of OSG headers that are disabling warnings, but never set them back to their original setting. The headers

Re: [osg-users] Compiling in MSVC with OSG_DISABLE_MSVC_WARNINGS defined causes warnings in user code to remain disabled

2014-01-08 Thread Judson Weissert
Hi Robert, Thank you for your reply, I appreciate the amount of time you dedicate to the mailing list, and the OSG project in general. On 1/8/2014 12:19 PM, Robert Osfield wrote: Hi Judson, Over the years we've found VS products lots of unhelpful warnings are perfectly correct code so

Re: [osg-users] Compiling in MSVC with OSG_DISABLE_MSVC_WARNINGS defined causes warnings in user code to remain disabled

2014-01-08 Thread Judson Weissert
Hi Robert, On 1/8/2014 3:11 PM, Robert Osfield wrote: Hi Judson, The push/pop approach has to be protected by platform specifics and has to be splurged all over the code, and it can't be tested by everyone so it will invariable lead to build breakages as things don't get added/or removed.

Re: [osg-users] C++11 with OSG

2013-11-26 Thread Judson Weissert
Hi deniz, I am not sure how you came to that conclusion. I suggest upgrading to VS2013 as soon as possible, and test your application with it. You can set policy to support older, non-c++11 compliant compilers if you wish, but that decision should not prevent you from moving to new compilers

Re: [osg-users] [osgText] Visual Studio 2013 (VS11) compatibility

2013-11-21 Thread Judson Weissert
and svn/trunk. Robert. On 20 November 2013 00:36, Judson Weissert jud...@mfrac.com mailto:jud...@mfrac.com wrote: Hello, I was wondering if anyone has compiled OSG on Visual Studio 2013 yet? I am compiling OSG 3.2.1 on Visual Studio 2013, and encountered a build error in src

[osg-users] [osgText] Visual Studio 2013 (VS11) compatibility

2013-11-19 Thread Judson Weissert
Hello, I was wondering if anyone has compiled OSG on Visual Studio 2013 yet? I am compiling OSG 3.2.1 on Visual Studio 2013, and encountered a build error in src/osgText/Glyph.cpp. It appears that std::min() and std::max() are not defined because the algorithm header was not included. See

Re: [osg-users] Using c++11 smartpointer instead of osg::ref_ptr?

2013-07-31 Thread Judson Weissert
On a related note, in boost, there is the concept of intrusive pointer (which I believe has similar semantics to ref_ptr). http://www.boost.org/doc/libs/1_54_0/libs/smart_ptr/intrusive_ptr.html It just rang some bells in my memory, so I figured I would post. Regards, Judson On 7/31/2013

Re: [osg-users] Using c++11 smartpointer instead of osg::ref_ptr?

2013-07-31 Thread Judson Weissert
Ah... I should have done a little more research. Seems like intrusive_ptr is already well considered and used within OSG. Judson On 7/31/2013 5:55 PM, Judson Weissert wrote: On a related note, in boost, there is the concept of intrusive pointer (which I believe has similar semantics

Re: [osg-users] Exporting OBJ file format

2013-07-18 Thread Judson Weissert
Hi Robert, On 7/18/2013 11:25 AM, Robert Osfield wrote: Hi Judson, If you haven't already tried it could you please test out the svn/trunk or recent developer version of the OSG. Sorry, I forgot to specify the version again... I was testing on Dev release 3.1.7. The OBJ spec from:

Re: [osg-users] Exporting OBJ file format

2013-07-15 Thread Judson Weissert
Joe, On 7/15/2013 10:04 AM, Joe Lyga wrote: I've never had that much success exporting models to .OBJ and getting them to work and display correctly afterwards. If you want to save models out of Sketchup or 3DS Max into something that can be converted to an OpenSceneGraph format, I've found

[osg-users] Exporting OBJ file format

2013-07-09 Thread Judson Weissert
Hello, I was recently trying out the OBJ plugin for exporting a model, and it ended up specifying line vertices using syntax one would expect when specifying faces. i.e., The exported file contained a number of lines such as: l 2261// 2262//2223 l 2263//2224 2264//2225 l 2265//2226

Re: [osg-users] Deprecating vertex indices in osg::Geometry

2013-06-18 Thread Judson Weissert
Hi Robert, Great work! I just have a few questions/comments. On 6/18/2013 7:42 AM, Robert Osfield wrote: Hi All, I have just finished a rather intensive bout of work on the new cleaned up osg::Geometry, one of the most challenging parts was providing a fallback for the deprecated array

Re: [osg-users] Deprecating vertex indices in osg::Geometry

2013-06-18 Thread Judson Weissert
Hi Robert, On 6/18/2013 10:58 AM, Robert Osfield wrote: Hi Judson, On 18 June 2013 15:21, Judson Weissert jud...@mfrac.com wrote: What is the difference between containsDeprecatedData() and checkForDeprecatedData()? I see that containsDeprecatedData() just checks the flag, what does

Re: [osg-users] Deprecating vertex indices in osg::Geometry

2013-06-18 Thread Judson Weissert
Hi Robert, On 6/18/2013 11:47 AM, Robert Osfield wrote: Hi Judson, On 18 June 2013 16:17, Judson Weissert jud...@mfrac.com wrote: I looked at the implementations now (the Geometry.cpp changes were not included in the online diff). Correct me if I am wrong, outside of the optimizer

Re: [osg-users] Pre-built dependencies for Visual Studio 2012

2013-06-14 Thread Judson Weissert
Hi Jan, and whomever else it may concern, For VC++ builds, it is also important to keep track of the iterator debugging settings for the build. Otherwise you may end up with incompatible binaries. Relevant flags are _SECURE_SCL and newer _ITERATOR_DEBUG_LEVEL. This is a bit of a wrinkle when

Re: [osg-users] [osgDB] Registry::writeNodeImplementation()

2013-06-11 Thread Judson Weissert
Robert, On 6/11/2013 5:08 AM, Robert Osfield wrote: Hi Judson, I have just checked in a change to Registry so it now sorts the list of ReaderWrite::ReadResult/WriteResult and returns the last result. The results are sorted on the Read/WriteStatus with these enums now ordered so that the most

Re: [osg-users] [osgDB] Registry::writeNodeImplementation()

2013-06-10 Thread Judson Weissert
Hi Robert, On 6/10/2013 4:48 AM, Robert Osfield wrote: Hi Judson, When you say the WriteResult is different could you explain what the result is in each case? Is there file written out OK in ech case. First pass, result status is FILE_NOT_HANDLED message is Warning: Write to path not

Re: [osg-users] [osgDB] Registry::writeNodeImplementation()

2013-06-10 Thread Judson Weissert
Hi Robert, Once again, thank you for your time. I continued to look into the scene export issues I was having, and here are some of my findings (against OSG 3.1.7 development release). I attached an alternate implementation of osgDB::Registry::writeNodeImplementation(). The same changes

Re: [osg-users] [osgDB] Registry::writeNodeImplementation()

2013-06-10 Thread Judson Weissert
21:12, Judson Weissert jud...@mfrac.com wrote: One of the major behavior changes is that once ERROR_IN_WRITING_FILE is encountered, no more attempts are made to write the file. This breaks the Chain-Of-Responsibility design pattern used by the plugins, it's up to plugins whether or not that can

[osg-users] [osgDB] Registry::writeNodeImplementation()

2013-06-07 Thread Judson Weissert
Hi, I was working on OSG export related code and I noticed some interesting problems with osgDB::Registry::writeNodeImplementation() and other similar functions within Registry.cpp. The first issue is that performing the same task twice gives different result. Reproduction case: 1. Create a

Re: [osg-users] Camera Manipulator or culling behavior change 3.1.2 vs 3.1.6

2013-05-29 Thread Judson Weissert
anything. Thanks again, Judson On 5/29/2013 4:19 AM, Robert Osfield wrote: Hi Judson, On 28 May 2013 20:36, Judson Weissert jud...@mfrac.com wrote: I just got the 3.1.7 developer release built. Running the osgviewer application with arguments --run-on-demand --screen 1 dumptruck.osgt results

Re: [osg-users] Camera Manipulator or culling behavior change 3.1.2 vs 3.1.6

2013-05-28 Thread Judson Weissert
Robert, This is great news! I will try out the new code as soon as possible and report back my findings. Thanks, Judson On 5/24/2013 5:42 AM, Robert Osfield wrote: Hi Judson. I have refactored the Viewer/CompositeViewer::checkNeedToDo() method so that it now calls a new

Re: [osg-users] OpenSceneGraph-3.1.7 developer release tagged

2013-05-28 Thread Judson Weissert
Hi Robert I just downloaded the new developer release and wanted to bring what I believe is a typo to your attention. See osg/src/osgViewer/config/PanormaicSphericalDisplay.cpp vs the header osg/include/osgViewer/config/PanoramicSphericalDisplay. I imagine PanormaicSphericalDisplay.cpp

Re: [osg-users] Camera Manipulator or culling behavior change 3.1.2 vs 3.1.6

2013-05-28 Thread Judson Weissert
on Windows 7 (Same machine and compiler settings as my previous tests). Regards, Judson On 5/28/2013 9:39 AM, Judson Weissert wrote: Robert, This is great news! I will try out the new code as soon as possible and report back my findings. Thanks, Judson On 5/24/2013 5:42 AM, Robert

Re: [osg-users] Camera Manipulator or culling behavior change 3.1.2 vs 3.1.6

2013-05-23 Thread Judson Weissert
that could be negative. Do you have an idea of how to reproduce the problem now? Once I can reproduce it I'll be able to work out the best west to resolve the problem. Robert. On 22 May 2013 22:50, Judson Weissert jud...@mfrac.com wrote: Robert, I found the revision that caused the regression

Re: [osg-users] Camera Manipulator or culling behavior change 3.1.2 vs 3.1.6

2013-05-23 Thread Judson Weissert
of triggering the behavior. Sorry for my confusion, Judson On 5/23/2013 2:34 PM, Robert Osfield wrote: Thanks for the code reproducing the problem, I'm just turning in for the day so will have a look at trying to reproduce the issue tomorrow. On 23 May 2013 18:32, Judson Weissert jud...@mfrac.com

[osg-users] Camera Manipulator or culling behavior change 3.1.2 vs 3.1.6

2013-05-22 Thread Judson Weissert
Hello, I have recently upgraded to the 3.1.6 development release of the OSG library (from 3.1.2) and encountered some behavior changes when manipulating a model using the Trackball Manipulator (I did derive from it though and modify some non-mouse related features). Compiled by VS2010,

Re: [osg-users] Camera Manipulator or culling behavior change 3.1.2 vs 3.1.6

2013-05-22 Thread Judson Weissert
Robert, On 5/22/2013 10:23 AM, Robert Osfield wrote: HI Judson, I have done a refactor of osgViewer's internally handling of mouse events to allow for seamless handling of distortion correction set ups, there is chance that this might have broken something that I haven't yet observed in my own

Re: [osg-users] Camera Manipulator or culling behavior change 3.1.2 vs 3.1.6

2013-05-22 Thread Judson Weissert
to the osgviewer application. Thus, there is still a piece of the puzzle that I am missing. Regards, Judson On 5/22/2013 12:10 PM, Judson Weissert wrote: Robert, On 5/22/2013 10:23 AM, Robert Osfield wrote: HI Judson, I have done a refactor of osgViewer's internally handling of mouse events to allow

Re: [osg-users] Camera Manipulator or culling behavior change 3.1.2 vs 3.1.6

2013-05-22 Thread Judson Weissert
Robert, I have made some progress. The problem appears to be caused by an eventTimeDelta of zero which is calculated within StandardManipulator::performMovement(). It eventually results in a divide by zero and the propagation of non-finite value(s) through the remainder of the call chain.

Re: [osg-users] Camera Manipulator or culling behavior change 3.1.2 vs 3.1.6

2013-05-22 Thread Judson Weissert
, Judson On 5/22/2013 3:02 PM, Judson Weissert wrote: Robert, I have made some progress. The problem appears to be caused by an eventTimeDelta of zero which is calculated within StandardManipulator::performMovement(). It eventually results in a divide by zero and the propagation of non-finite value

Re: [osg-users] [Viewer] Detecting mouse move

2013-05-21 Thread Judson Weissert
Asher, The GUIEventAdapter::DRAG event is not what you are looking for? Regards, Judson On 5/20/2013 5:00 PM, Asher Kamiraze wrote: Hi all, In some of my application, I would like to detect when a clic + mouse move event happen. My goal is to display on screen during the clic + mouse move

Re: [osg-users] Dinamic Line Drawing

2013-05-10 Thread Judson Weissert
Hi Patrick, On 5/9/2013 9:16 PM, Patrick Keenan wrote: Hi, This post was really helpful for me but I still couldn't add points on the fly either. A few edits made it happen so I'm attaching my M_OSG_line_strip class. To use the class I have the following in my CreateScene() Code:

Re: [osg-users] osgWidget::EventInterface possible memory leak

2013-04-16 Thread Judson Weissert
Robert, On 4/16/2013 5:26 AM, Robert Osfield wrote: Hi Judson and Jeremy, On 15 April 2013 22:15, Judson Weissert jud...@mfrac.com mailto:jud...@mfrac.com wrote: I know the feeling :) I am having difficulties trying to figure out the likelihood of circular references if the type

[osg-users] osgWidget::EventInterface possible memory leak

2013-04-15 Thread Judson Weissert
Hello, I have been experimenting with the osgWidget library recently, and came across what I believe to be a memory leak. I added a break point to the osgWidget::Callback destructor, and it is never called when running the osgwidgetcanvas example program (the constructor is called a number of

Re: [osg-users] osgWidget::EventInterface possible memory leak

2013-04-15 Thread Judson Weissert
Hi Jeremy, Thank you for the reply, I appreciate the amount of time and effort you have put into osgWidget library over the years. On 4/15/2013 2:07 PM, Jeremy Moles wrote: On 04/15/2013 12:37 PM, Judson Weissert wrote: Hello, I have been experimenting with the osgWidget library recently

Re: [osg-users] VBO fallback behavior and virtual machines

2013-03-22 Thread Judson Weissert
On 3/22/2013 4:56 AM, Robert Osfield wrote: Hi Judson, On 21 March 2013 20:26, Judson Weissert jud...@mfrac.com wrote: There is an interesting distinction between needing to dirty a display list (e.g., Drawable::dirtyDisplayList()) versus having to dirty a primitive when using VBO (e.g., Array

Re: [osg-users] VBO fallback behavior and virtual machines

2013-03-21 Thread Judson Weissert
with atiumdag 9.2.0.0 (Catalyst 12.10) driver - Host Windows 7 64-bit - Guest Windows 7 Ultimate N 64-bit Thanks, Judson On 3/20/2013 10:36 PM, Garth D wrote: Hi Judson, On 20/03/13 09:57, Judson Weissert wrote: Has anyone had success viewing their models using VirtualBox? I can confirm

Re: [osg-users] VBO fallback behavior and virtual machines

2013-03-21 Thread Judson Weissert
Hi Robert, On 3/21/2013 10:44 AM, Robert Osfield wrote: Hi Judson, On 21 March 2013 13:56, Judson Weissert jud...@mfrac.com wrote: Thank you for the information. Knowing that you got it to work in an embedded (non-fullscreen) window w/ 3D acceleration enabled is helpful. I should have posted

Re: [osg-users] VBO fallback behavior and virtual machines

2013-03-21 Thread Judson Weissert
Robert, Excellent, I will begin testing it now and report back. Thank you, Judson On 3/21/2013 12:06 PM, Robert Osfield wrote: HI Judson, On 21 March 2013 15:23, Judson Weissert jud...@mfrac.com wrote: It looks like osg::State already has that flag. See osg::State

Re: [osg-users] VBO fallback behavior and virtual machines

2013-03-21 Thread Judson Weissert
() in client code could be missing (because the primitive array was dirtied instead of the display list for instance). Not that this is a major issue, but it is something to think about when fallback is a possibility. Regards, Judson On 3/21/2013 12:49 PM, Judson Weissert wrote: Robert, Excellent, I

Re: [osg-users] VBO fallback behavior and virtual machines

2013-03-20 Thread Judson Weissert
of other stuff too, but redirect the output to a file and then browse through. This should tell you what the OSG has got back from the driver. Robert. On 19 March 2013 23:27, Judson Weissert jud...@mfrac.com wrote: Hello, I have been testing in VirtualBox recently, and encountered two problems that I

Re: [osg-users] VBO fallback behavior and virtual machines

2013-03-20 Thread Judson Weissert
inside the Virtual Environment. I am assuming the crash is the same, I need to do some additional debugging. Regards, Judson On 3/20/2013 9:57 AM, Judson Weissert wrote: Hi Robert, Thank you for the suggestion. I have attached the notify log. In summary, the log includes a number of entries

[osg-users] VBO fallback behavior and virtual machines

2013-03-19 Thread Judson Weissert
Hello, I have been testing in VirtualBox recently, and encountered two problems that I was hoping someone might recognize. Note: The problems do not occur outside of a virtual environment. 1. I have geometry in my model where I call osg::Geometry::setUseVertexBufferObjects(true), but the

[osg-users] [osgViewer] ON_DEMAND frame updates

2013-03-13 Thread Judson Weissert
Hello, I have been working on switching over to ON_DEMAND frame updates while using osgViewer::Viewer and I encountered the following problems (all of these issues are specific to ON_DEMAND frame updates): 1. Some of the event handlers such as osgViewer::HelpHandler, and

Re: [osg-users] [osgViewer] ON_DEMAND frame updates

2013-03-13 Thread Judson Weissert
that there is a race condition somewhere that I have not tracked down. Regards, Judson On 3/13/2013 2:06 PM, Judson Weissert wrote: Hello, I have been working on switching over to ON_DEMAND frame updates while using osgViewer::Viewer and I encountered the following problems (all of these issues

Re: [osg-users] [osgViewer] ScreenCaptureHandler::handle() missing break statement

2012-12-05 Thread Judson Weissert
Robert, On 12/5/2012 5:16 AM, Robert Osfield wrote: On 4 December 2012 18:07, Judson Weissert jud...@mfrac.com mailto:jud...@mfrac.com wrote: The following problems occurred when I tried that: 1. It exposed the missing break statement issue that you have subsequently fixed. 2

Re: [osg-users] [osgViewer] ScreenCaptureHandler::handle() missing break statement

2012-12-04 Thread Judson Weissert
Hi Robert, Thank you for applying the change to trunk, I really appreciate it. On 12/4/2012 4:03 AM, Robert Osfield wrote: Also, I was wondering if it would be a reasonable enhancement to disable, for example, the continuous capture feature by simply setting the _keyEvent (e.g.,

Re: [osg-users] [osgViewer] ScreenCaptureHandler::handle() missing break statement

2012-12-04 Thread Judson Weissert
Robert, On 12/4/2012 12:21 PM, Robert Osfield wrote: Hi Judson. On 4 December 2012 14:56, Judson Weissert jud...@mfrac.com mailto:jud...@mfrac.com wrote: I meant for cases where the event handler performs multiple tasks. i.e., provide the ability to disable continuous capture

[osg-users] [osgViewer] ScreenCaptureHandler::handle() missing break statement

2012-12-03 Thread Judson Weissert
Hello, I was using the osgViewer::ScreenCaptureHandler today for the first time. While I was trying to disable the continuous capture feature, I stumbled upon what I believe to be a bug. The switch statement case for osgGA::GUIEventAdapter::FRAME is missing a break statement, so the KEYUP

Re: [osg-users] Camera manipulator velocity and home() calculation affected after scaling nodes (partially resolved)

2012-08-28 Thread Judson Weissert
On 8/27/2012 3:14 PM, Jeremy Moles wrote: A Drawable can have a special ComputeBoundsCallback() (something like that, I'm on my phone right now and can't look it up), so you could use that as well... Here is the code I came up with after your suggestion that does resolve my problem (I attach

[osg-users] Camera manipulator velocity and home() calculation affected after scaling nodes

2012-08-27 Thread Judson Weissert
not make the overall volume of the scene any larger (as far as I can tell). Additional information: Lib Version: OpenSceneGraph 3.1.2 (Compiled with VS2010 on Windows 7 64-bit) Manipulator: osgGA::TrackballManipulator Any hints/tips would be greatly appreciated. Thank you, Judson Weissert

Re: [osg-users] Camera manipulator velocity and home() calculation affected after scaling nodes

2012-08-27 Thread Judson Weissert
On 8/27/2012 2:22 PM, Jeremy Moles wrote: On Mon, 2012-08-27 at 13:54 -0400, Judson Weissert wrote: Hello, I was hoping someone could help me with a camera manipulator/scaling problem that I have been having. I have a scene graph that contains geometry representing a hydraulic fracture

Re: [osg-users] Weird problem with osgText::Text3D

2011-03-08 Thread Judson Weissert
Hi, I have also experienced problems with Text3D. Specifically, problems with character spacing (possibly kerning related?) where letters will end up overlapping for certain strings. I think 2.9.10 exhibits the overlapping behavior. I also updated to the latest trunk revision at the time (which

Re: [osg-users] Hiding and Showing a Node with Key Press

2011-02-18 Thread Judson Weissert
If you associate a node mask to each type of node that may need to be hidden using setNodeMask(), you can then modify the cull mask of the camera to show/hide the nodes accordingly. osg::Camera::setCullMask (mask) - would be called when the keyboard button is pressed. osg::Node::setNodeMask