[osg-users] [osgPPU] Character animation

[Erick Diaz]

Hi,

I'm sure that you already have seen this question a lot of times, but after 
several hours of research i didn't find a concrete solution... 

I have an animated character en 3d max / Maya, is a skeleton based animation, 
that i already loaded in Away3D (is not a big and complicated rig), my question 
is...

which is the recommended way to export it in OSG for 3d Max and/or Maya, with 
the animation and calling animation clips in the engine...

I appreciate any help!!! 

Thank you!

Cheers,
Erick :D

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=13320#13320





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Help. KeyboardEventHandler and native keyboard layout bug in Linux

[Maxim Gammer]

Hi Robert,

i test new GraphicsWindowX11.cpp .

2009/6/2 Melchior FRANZ :
> * Melchior FRANZ -- Monday 01 June 2009:
>> My keyboard doesn't have a keypad, so I can only test the other keys.
>
> ... but everything else worked. And we'll soon find out if there are
> still keypad problems. The current solution is already infinitely
> better than what is in SVN/HEAD, so I'd commit.
>
> Thanks for the fix!
>
> m.
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>



-- 
Maxim Gammer
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Can I change the plugin directory structure?

[rpingry]

> Why is it hard? Just svn add the whole directory, that should add all
contents and subdirectories by default... Unless I'm missing something?

Well, which Plugin directory am I supposed to add?  If I add a particular
plugin directory with a given name, and then I do an update and the plugin
version changes, then the folder name is not the same anymore.  Do I add the
new plugin folder and delete the old one?  Perhaps use SVN to change the
directory name (which essentially does the same thing)?



On Mon, Jun 1, 2009 at 8:40 PM, Jean-Sébastien Guay <
jean-sebastien.g...@cm-labs.com> wrote:

> Hi Rick,
>
>  So for the examples, is there any way to set the Working Directory for
>> debugging?  It is actually pretty easy to select all of the apps and
>> examples and then set properties for all configurations at one time, so that
>> is not such a big deal, but I was curious.
>>
>
> I don't know of any way to set it for all examples in one go, no. Sorry...
>
>  So, I am starting to get the idea of the version number on the folder.  In
>> our environment, we have separate folders for debug and release folders.  I
>> know that OSG puts them all in one folder.  Our bat files break out the OSG
>> files to go to our debug and release folders.  Is there an easy way to break
>> them up to separate debug and release folders rather than compiling to a
>> single folder?
>>
>
> I'd like that too actually. Right now what I do is:
> 1. Clean destination directory.
> 2. Build INSTALL target in debug.
> 3. Run script to copy debug binaries to somewhere.
> 4. Clean destination directory.
> 5. Build INSTALL target in release.
> 6. Run script to copy release binaries to somewhere.
>
> It's kind of a pain, but we only update OSG on stable releases, so I don't
> have to do it too often. If your project lives on the bleeding edge I can
> see how that would be more painful, though again you could script all that
> with the devenv /build command line I gave you in the other message...
>
> But it would be nice of OSG's CMake scripts supported this in some way. It
> just doesn't bug me enough personally to take the time to implement it :-)
>
>  Finally, we are moving these files to a stable bin folder, and then we are
>> checking them in to our own SVN repository.  Just copying the bin folder
>> with a versioned number plugin folder makes that really hard.  Any ideas?
>>
>
> Why is it hard? Just svn add the whole directory, that should add all
> contents and subdirectories by default... Unless I'm missing something?
>
>
> Hope this helps,
>
> J-S
> --
> __
> Jean-Sebastien Guayjean-sebastien.g...@cm-labs.com
>   http://www.cm-labs.com/
>http://whitestar02.webhop.org/
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] OSG users in Colorado

[Alan Dickinson]

Hi Paul,

I am in Highlands Ranch on the south side of Denver. 

Alan Dickinson
emeraldfox-att-mac-dot-com

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=13323#13323





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Can I change the plugin directory structure?

[Jean-Sébastien Guay]

Hi Rick,

So for the examples, is there any way to set the Working Directory for 
debugging?  It is actually pretty easy to select all of the apps and 
examples and then set properties for all configurations at one time, so 
that is not such a big deal, but I was curious.


I don't know of any way to set it for all examples in one go, no. Sorry...

So, I am starting to get the idea of the version number on the folder.  
In our environment, we have separate folders for debug and release 
folders.  I know that OSG puts them all in one folder.  Our bat files 
break out the OSG files to go to our debug and release folders.  Is 
there an easy way to break them up to separate debug and release folders 
rather than compiling to a single folder?


I'd like that too actually. Right now what I do is:
1. Clean destination directory.
2. Build INSTALL target in debug.
3. Run script to copy debug binaries to somewhere.
4. Clean destination directory.
5. Build INSTALL target in release.
6. Run script to copy release binaries to somewhere.

It's kind of a pain, but we only update OSG on stable releases, so I 
don't have to do it too often. If your project lives on the bleeding 
edge I can see how that would be more painful, though again you could 
script all that with the devenv /build command line I gave you in the 
other message...


But it would be nice of OSG's CMake scripts supported this in some way. 
It just doesn't bug me enough personally to take the time to implement 
it :-)


Finally, we are moving these files to a stable bin folder, and then we 
are checking them in to our own SVN repository.  Just copying the bin 
folder with a versioned number plugin folder makes that really hard.  
Any ideas?


Why is it hard? Just svn add the whole directory, that should add all 
contents and subdirectories by default... Unless I'm missing something?


Hope this helps,

J-S
--
__
Jean-Sebastien Guayjean-sebastien.g...@cm-labs.com
   http://www.cm-labs.com/
http://whitestar02.webhop.org/
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Can I change the plugin directory structure?

[rpingry]

> You say your examples are in bin\Release. This is not the case for me;
there
> is no bin\Release in my build dir. The release build of my osganimate.exe
> file is in "\bin". Not sure why yours would be elsewhere,
but
> this appears to be the source of your problem. What CMake variables did
you
> change from their default?

AHA:  It was OSG_MSVC_VERSIONED_DLL  If you leave it in its default "on"
position, it makes the "linker > General > Output File" to something like:
"\bin\Release\..\osghud.exe"

Somewhere along the line, probably as I was kicking against the pricks
trying to avoid having to deal with versioned dlls, I turned
OSG_MSVC_VERSIONED_DLL off.  After doing that, it set "linker > General >
Output File" to something like:
"\bin\Release\osghud.exe"


So for the examples, is there any way to set the Working Directory for
debugging?  It is actually pretty easy to select all of the apps and
examples and then set properties for all configurations at one time, so that
is not such a big deal, but I was curious.

So, I am starting to get the idea of the version number on the folder.  In
our environment, we have separate folders for debug and release folders.  I
know that OSG puts them all in one folder.  Our bat files break out the OSG
files to go to our debug and release folders.  Is there an easy way to break
them up to separate debug and release folders rather than compiling to a
single folder?

Finally, we are moving these files to a stable bin folder, and then we are
checking them in to our own SVN repository.  Just copying the bin folder
with a versioned number plugin folder makes that really hard.  Any ideas?

Thanks
-- Rick


> brought up Properties and specified
> OSG_NOTIFY_LEVEL=DEBUG_FP in the environment, then I hit ctrl-f5 to run.
Wow, that is cool, how do you do that?  In the C++ Preprocessor Settings?
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Picking primitive subset

[Andrew Cunningham]

One thing that makes the primitiveIndex field of the intersection classes 
significantly less useful that it could be is that the Intersector decomposes 
QUADS etc into triangles. This means some additional housekeeping to keep track 
of what the index relates to

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=13319#13319





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

[osg-users] Render-to-texture question.

[Guy Volckaert]

Hi,

I was wondering if you can provide me with some guidance regarding RTT. BTW: I 
read and understood the osgMultipleRenderTargets example very well (hopefully 
8)). However, I was wondering if it would be possible to simply it a little for 
my app.

My application has multiple slave cameras using osgViewer (not composite 
viewer). Each camera can show the scene using a different sensor mode (i.e 
thermal, day, nigt-vision, etc). 

On a per camera basis,  I need to render the scene to a texture. Each of those 
cameras then render their respective image to a simple quad in their own 
window. 

The questions is: can I do this without adding a seperate RTT camera for each 
slave camera?

Will enabling RTT for each slave camera and drawing a simple quad in the 
PostDrawCallback/FinalDrawCallback work (using direct opengl calls)? 

Do I absolutely need to add another camera in the scene to make RTT work?

Maybe if I understood the render-to-texture process in the camera a little 
better, especially when it starts and when it ends, then I would have a better 
idea if what I'm trying to is possible. 

Any help would be appreciated.

Cheers,
Guy

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=13317#13317





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Picking primitive subset

[Andrew Cunningham]

Paul,
I already have the two geometries sharing the same vertex array. But some 
"decorations" to show a "picked state" are mutually exclusive. For example, 
showing the "picked" primitives subset as wireframe ( not filled) is not 
possible as the same primitives will be present as "filled" in the default set.

I suppose the sensible thing is to pick a decoration that can overlay the 
existing geometry (e.g all picked elements are outlined in a thick line) or are 
a different color with a larger polygon offset.

Andrew

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=13316#13316





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

[osg-users] Q for getCoordinateFrame in special and matrixManipulator in general

[Christian Sam]

Hi community, i'm currently trying to understand how the various 
camera-manipulators work (trackball, terrain, ufo, etc.) and several questions 
arrived:

- the first thing that confused me was, that Y/Z-vector directions are now the 
openGL-way. (is there a reason why OSG normally uses Y as forward-vector?)

- i also often encounterd the functions "getCoordinateFrame(Vec3&)" and 
"getUpVector(cf)", e.g:

Code:

CoordinateFrame eyePointCoordFrame = getCoordinateFrame( eye )
if (intersect(eye+getUpVector(eyePointCoordFrame)*distance,...



i have not much practice with matrix transformations, so its a little bit hard 
for me to understand the sense of this, but i assume the following: eye is the 
position of the camera, and the camera has it's own local coordinate-system. 
getCoordinateFrame() / getXVector() provide the world coordinates from such 
local coordinate frame. 

i looked up the implentation of getCoordinateFrame(), but i couldn't find out 
how it is accomplished, can you explain me how this is done?



Thanks in advance, 
Christian

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=13315#13315





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] OSG users in Colorado

[Paul Martz]

Hi Alan -- Are you down in the Springs area? Chris is west of Denver and
Mike Weiblen and I are both in Boulder County. I know there are some other
OSG users in the Springs but your name doesn't ring a bell.

Paul Martz
Skew Matrix Software LLC
http://www.skew-matrix.com
+1 303 859 9466

-Original Message-
From: osg-users-boun...@lists.openscenegraph.org
[mailto:osg-users-boun...@lists.openscenegraph.org] On Behalf Of Alan
Dickinson
Sent: Monday, June 01, 2009 4:15 PM
To: osg-users@lists.openscenegraph.org
Subject: Re: [osg-users] OSG users in Colorado

Hi Chris,

I am an OSG user/developer here in the Colorado front-range area and I am
interested in getting together to meet others in the area.

Please let me know what you are planning.

Thanks,

Alan Dickinson

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=13313#13313





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] OSG users in Colorado

[Alan Dickinson]

Hi Chris,

I am an OSG user/developer here in the Colorado front-range area and I am 
interested in getting together to meet others in the area.

Please let me know what you are planning.

Thanks,

Alan Dickinson

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=13313#13313





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Picking primitive subset

[Paul Martz]

> Also , I am not sure how best to go about showing the selection. I
> could, for example,  break the geometry into "selected" and "non-
> selected" geonodes and shuffle the primitives back and forth between
> these two based on what has been selected or de-selected.

It sounds like you're saying you would copy the picked data into another
Geometry. There is really no need for that. Just have two Geometries (one
for the normal data display, and one for pick highlighting with a decorator
or StateSet mod of your choosing), and make the two Geometry objects share
the same vertex array.
   -Paul

___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] per-facet normals for "flat" facets

[Butler, Lee Mr CIV USA USAMC]

Paul,

My CAD data comes to me as a triangle "soup" without surface normals.
Right now it comes to me as wavefront OBJ format.  

Item 1: I would rather not display any "smoothing".  That looks like it
will take mods to the obj plugin to avoid the smoothing (unless someone
can point me at something else).

Item 2: The majority of normals point along one of the 6 major axis
directions (or a small number of other directions).  I could easily
quantize to byte (not float) normals and be quite happy.  But I think
that gets me writing shaders, which I was hoping to avoid.

I had thought there was a way to tell OpenGL to use an index indirection
table for elements.  My thought was I could load a small array of
normals, an array of vertexes, and an array of indexes which maps the
vertex index to the normal index.  Alas, I don't seem to be able to
figure out the nuance of this in OSG (or OpenGL) at the moment.

Lee

PS.  If I could afford an NVIDIA Quadro FX 5800 for all my systems I'd
just load the geometry onto the graphics card and be happy.

On Mon, 2009-06-01 at 14:15 -0600, Paul Martz wrote:
> Your problem seems to stem from having to repeat vertices multiple times so
> that each can have its own vertex. For example, let's say you need to repeat
> each vertex 4 times because it is shared by 4 different facets. This means
> you have xyz vert/norm (24 bytes) * 4 * 20M = ~2GB. Do I understand the
> issue correctly?
> 
> You don't want to specify the normal once per facet because that will send
> you down the OpenGL slow path (setting normal binding to
> BIND_PER_PRIMITIVE). But this would be the easiest change and fastest course
> of action, and with display lists on, this could still produce acceptable
> performance.
> 
> There are normal compression schemes. I patented one while at HP that is
> lossy but allows you to specify a variable amount of compression. In our
> work, we found that a 6:1 compression ration (store the normal as a 2-byte
> short) still produced pretty good visual results. If you search for my name
> in any patent search engine you can find more info. This algorithm was
> storage-efficient but not computationally efficient.
> 
> For a computationally efficient algorithm, try representing the xyz
> components as 10 bit signed ints stored in a single word and then unpack
> them in a shader.
> 
> Special data types allow other types of normal compression. For example,
> bump maps, or normals for heightfield data, only need two components. The
> third can always be derived.
> 
> Paul Martz
> Skew Matrix Software LLC
> http://www.skew-matrix.com
> +1 303 859 9466
> 
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

[osg-users] Separate Viewer for FBOs? (UNCLASSIFIED)

[Kaniarz, John Mr CIV USA AMC]

Classification: UNCLASSIFIED
Caveats: NONE

I am working on an application that looks at large data sets. The scene
uses shadow mapping with a large number of cameras (approx 20). This
really hurts the frame rates. The data set rarely changes. Because of
this I would like to move my pre-render FBO cameras out of the scene
graph and update them only when the scene changes (so they don't re-draw
the same thing every frame). I'm not sure how to proceed. Should I use a
switch node on the camera branch? Should I use a separate Viewer object?
What about CompositeViewer?

Thanks,
John
Classification: UNCLASSIFIED
Caveats: NONE


___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Picking primitive subset

[Andrew Cunningham]

Hi Paul,
I suppose I am unsure of "OSG best practices"  to use when picking of 
primitives. With osg::Nodes I am using "userdata" quite effectively to relate 
an picked osg::node back to my data model - but with primitives it is not quite 
so clear what the best OSG way would be especially when dealing with 500K 
primitives.  My naive approach would be to store a lookup relating primitive 
index to my C++ model object so I can extract my C++ object from a primitive 
pick index. 



Also , I am not sure how best to go about showing the selection. I could, for 
example,  break the geometry into "selected" and "non-selected" geonodes and 
shuffle the primitives back and forth between these two based on what has been 
selected or de-selected.


... 

Thank you!

Cheers,
Andrew

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=13308#13308





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Set fog in the canera StateSet

[Tueller, Shayne R Civ USAF AFMC 519 SMXS/MXDEC]

Cristina,

Do you have a code snippet you can provide us?

The following works for our case for each camera in the scene. We are using
the compositeViewer where each view added to the viewer has its own camera.

fog = new osg::Fog();
fog->setMode(osg::Fog::EXP2);
fog->setFogCoordinateSource(osg::Fog::FRAGMENT_DEPTH);
fog->setColor(fogcolor);
view->getCamera()->getOrCreateStateSet()->setAttributeAndModes(fog,
osg::StateAttribute::ON);

You should be able to set a different fog state for each camera in turn...

-Shayne

-Original Message-
From: osg-users-boun...@lists.openscenegraph.org
[mailto:osg-users-boun...@lists.openscenegraph.org] On Behalf Of Cristina
Paponi
Sent: Monday, June 01, 2009 12:22 PM
To: osg-users@lists.openscenegraph.org
Subject: [osg-users] Set fog in the canera StateSet

Hi,

Could you please help me with the following problem. In my scene I have 2
cameras one for day and one for thermo.
Because the fog will appear different in day and thermo, I tried to assign
the fog to the camera's StateSet.
When I try to set the fog attribute to the camera StateSet there is no
effect, but if I set the fog to the root of the scene's StateSet everything
is fine.
Is it possible to set the fog in the camera ?

Thank you!

Cheers,
Cristina

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=13293#13293





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org


smime.p7s
Description: S/MIME cryptographic signature
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Help. KeyboardEventHandler and native keyboard layout bug in Linux

[Melchior FRANZ]

* Melchior FRANZ -- Monday 01 June 2009:
> My keyboard doesn't have a keypad, so I can only test the other keys.

... but everything else worked. And we'll soon find out if there are
still keypad problems. The current solution is already infinitely
better than what is in SVN/HEAD, so I'd commit.

Thanks for the fix!

m.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] per-facet normals for "flat" facets

[Paul Martz]

Your problem seems to stem from having to repeat vertices multiple times so
that each can have its own vertex. For example, let's say you need to repeat
each vertex 4 times because it is shared by 4 different facets. This means
you have xyz vert/norm (24 bytes) * 4 * 20M = ~2GB. Do I understand the
issue correctly?

You don't want to specify the normal once per facet because that will send
you down the OpenGL slow path (setting normal binding to
BIND_PER_PRIMITIVE). But this would be the easiest change and fastest course
of action, and with display lists on, this could still produce acceptable
performance.

There are normal compression schemes. I patented one while at HP that is
lossy but allows you to specify a variable amount of compression. In our
work, we found that a 6:1 compression ration (store the normal as a 2-byte
short) still produced pretty good visual results. If you search for my name
in any patent search engine you can find more info. This algorithm was
storage-efficient but not computationally efficient.

For a computationally efficient algorithm, try representing the xyz
components as 10 bit signed ints stored in a single word and then unpack
them in a shader.

Special data types allow other types of normal compression. For example,
bump maps, or normals for heightfield data, only need two components. The
third can always be derived.

Paul Martz
Skew Matrix Software LLC
http://www.skew-matrix.com
+1 303 859 9466

___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Osg stereo problems!! Help!!!

[Yongjin Li]

Dear Robert,

I am sorry, I really misread you meaning. :-* 

Are you have some suggestions to solve the two problems?

Thank you!

Cheers,
Yongjin

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=13304#13304





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Problems using setResizeNonPowerOfTwoHint(false);

[Gilbert, Daniel R.]

Robert, Gordon,

This issue looks like it might be the same one I experienced back in February 
(http://forum.openscenegraph.org/viewtopic.php?t=1656)

I never took it further as my need soon became OBE, but at least it's another 
potential data point.

-- Dan


> -Original Message-
> From: Tomlinson, Gordon [mailto:gtomlin...@overwatch.textron.com]
> Sent: Monday, June 01, 2009 11:22 AM
> To: OpenSceneGraph Users
> Subject: Re: [osg-users] Problems using setResizeNonPowerOfTwoHint(false);
> 
> Hi Robert
> 
> Ok we will give it a go and get back to you
> 
> 
> Gordon
> Product Manager 3d
> __
> Gordon Tomlinson
> Email  : gtomlinson @ overwatch.textron.com
> __
> 
> 
> -Original Message-
> From: osg-users-boun...@lists.openscenegraph.org [mailto:osg-users-
> boun...@lists.openscenegraph.org] On Behalf Of Robert Osfield
> Sent: Monday, June 01, 2009 12:50 PM
> To: OpenSceneGraph Users
> Subject: Re: [osg-users] Problems using setResizeNonPowerOfTwoHint(false);
> 
> Hi Gordon,
> 
> I've just tracked down the original posts from Mark and have looked at his
> sample and suggested fix.  The fix hasn't been merged, nor a variation on
> it.  I vaguely remember the thread, but not any resolution, it might be
> that I was swept away by other work so didn't chase it up.
> 
> I've just tried to reproduce the problem using the Sample.cpp but
> unfortunately I can't reproduce the problem on my ATI based system as it
> does have full support for non power of two with mipmapping.  I've
> followed the logic of the related generate mipmap code and can see how it
> would fail, and why Mark's suggest should address this failure.
> 
> The failure looks to have been due to introduction of more "advanced"
> mipmap generation support, which probably worked in some usage
> combinations but not all.
> 
> I have taken the essence of Mark's fixed and applied to Texture2D.cpp,
> could you test this as I can't reproduce the problem to know whether it's
> been fixed or not.
> 
> Robert.
> 
> On Mon, Jun 1, 2009 at 2:39 PM, Tomlinson, Gordon
>  wrote:
> > Hi
> >
> > Were having problems with textures that are non power of 2 or power 2
> > if we use   m_texture->setResizeNonPowerOfTwoHint(false);
> > we get no texture
> >
> > The engineer who spotted this says this post
> > http://www.mail-archive.com/osg-users@lists.openscenegraph.org/msg1520
> > 6.html had a fix but looks like it never made it submission or was
> > maybe rejects , does any one elsehave this issue,  was this fix  ever
> > applied  ?
> >
> > Fails in 2.8
> > Works in 2.3/4
> >
> >
> >
> >
> >
> >
> >
> >
> >
> > Gordon
> > Product Manager 3d
> > __
> > Gordon Tomlinson
> > Email  : gtomlinso...@ overwatch.textron.com
> > __
> > (C): (+1) 571-265-2612
> > (W): (+1) 703-437-7651
> >
> > "Self defence is not a function of learning tricks but is a function
> > of how quickly and intensely one can arouse one's instinct for
> > survival"
> > - Master Tambo Tetsura
> >
> >
> > ___
> > osg-users mailing list
> > osg-users@lists.openscenegraph.org
> > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.
> > org
> >
> >

___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] per-facet normals for "flat" facets

[Thrall, Bryan]

Butler, Lee Mr CIV USA USAMC wrote on Monday, June 01, 2009 1:55 PM:

> I'm looking for ways to efficiently store/display geometry with "flat"
> facets.  That is to say, I want "all" creases (no interpolated
normals).
> I'm reading some hefty geometry (10-20M polys) for display (Currently
in
> OBJ format).  There are only hundreds of unique normals.  The OBJ
loader
> tristrips everything and computes per-vertex normals.
> 
> Since I'm bumping up against the memory address limit on 32bit
machines
> when using this geometry, I'd *really* like to recoup the storage for
> all those (redundant) normals.  I think using short ints for 'normal
> indexes' instead of per-vertex normals would buy me a fair bit of
space.
> 
> Can anyone offer any pointers/guidance?
> 
> Lee

Hi Lee,

I don't know anything about the OBJ loader except what 'osgconv --format
obj' tells me. Do the 'noTesselateLargePolygons' or 'noTriStripPolygons'
help?

$ osgconv --format obj
Plugin osgPlugins-2.9.5/osgdb_obj.dll
{
ReaderWriter : Wavefront OBJ Reader
{
features   : readNode writeObject writeNode 
extensions : .objAlias Wavefront OBJ
format
options: AMBIENT=  Set texture unit for
ambient texture
options: BUMP= Set texture unit for
bumpmap texture
options: DIFFUSE=  Set texture unit for
diffuse texture
options: DISPLACEMENT= Set texture unit for
displacement texture
options: OPACITY=  Set texture unit for
opacity/dissolve texture
options: REFLECTION=   Set texture unit for
reflection texture
options: SPECULAR= Set texture unit for
specular texture
options: SPECULAR_EXPONENT=Set texture unit for
specular exponent texture
options: noRotation  Do not do the default
rotate about X axis
options: noTesselateLargePolygonsDo not do the default
tesselation of large polygons
options: noTriStripPolygons  Do not do the default
tri stripping of polygons
}
}

HTH,
-- 
Bryan Thrall
FlightSafety International
bryan.thr...@flightsafety.com
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Help. KeyboardEventHandler and native keyboard layout bug in Linux

[Melchior FRANZ]

* Robert Osfield -- Monday 01 June 2009:
> Could you both do testing to check that things now
> work across the various locale combinations and applications.

My keyboard doesn't have a keypad, so I can only test the other keys.
(I'll try to find someone with keypad, but no promise. :-)

m.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Osg steteo problems!! Help!!!

[Robert Osfield]

HI Yongjin,

On Mon, Jun 1, 2009 at 7:48 PM, Yongjin Li  wrote:
> Dear Robert,
>
> I think the fusion distance is not the distance between left and right eyes 
> but is the distance from the center of two eyes to the sight convergence 
> point.

I'm afraid you've misread my email.  I didn't say the fusion distance
was the interoccular distance, please re-read.

Robert.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Picking primitive subset

[Paul Martz]

I'm not sure I understand your issue. If you can pick one quad, then you
should be able to pick several. Are you unsure of the user interface you
should implement? Or are you unsure of how you should track the picked
primitives? More info please.

Paul Martz
Skew Matrix Software LLC
http://www.skew-matrix.com
+1 303 859 9466

-Original Message-
From: osg-users-boun...@lists.openscenegraph.org
[mailto:osg-users-boun...@lists.openscenegraph.org] On Behalf Of Andrew
Cunningham
Sent: Monday, June 01, 2009 12:49 PM
To: osg-users@lists.openscenegraph.org
Subject: [osg-users] Picking primitive subset

Hi,
I have a geometry that is represented by perhaps 500K triangle and/or quad
primitives.

During user interaction, I need to pick ( using a selection rectangle) a
significant subset ( say 10K) of these primitives and "highlight" them (
simply turning the picked primitives wireframe would do).


Any suggestions on how to do this efficiently? I have OSG picking working
great with osg::Node objects but am a bit unsure of how to pick a subset of
primitive QUADS/TRIS from a single geometry.

Thank you!

Cheers,
Andrew

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=13297#13297





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

[osg-users] per-facet normals for "flat" facets

[Butler, Lee Mr CIV USA USAMC]

I'm looking for ways to efficiently store/display geometry with "flat"
facets.  That is to say, I want "all" creases (no interpolated normals).
I'm reading some hefty geometry (10-20M polys) for display (Currently in
OBJ format).  There are only hundreds of unique normals.  The OBJ loader
tristrips everything and computes per-vertex normals.  

Since I'm bumping up against the memory address limit on 32bit machines
when using this geometry, I'd *really* like to recoup the storage for
all those (redundant) normals.  I think using short ints for 'normal
indexes' instead of per-vertex normals would buy me a fair bit of space.

Can anyone offer any pointers/guidance?

Lee

___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Osg steteo problems!! Help!!!

[Yongjin Li]

Dear Robert,

I think the fusion distance is not the distance between left and right eyes but 
is the distance from the center of two eyes to the sight convergence point. 

The effect I looking for is that the scene and the prerender textures both have 
stereo effect.

The current codes are:
[code]#include "stdafx.h"

#include 
#include 
#include 

#include 
#include 

#include 

#include 

bool loadShaderSource(osg::Shader* obj, const std::string& fileName )
{
std::string fqFileName = osgDB::findDataFile(fileName);
if( fqFileName.length() != 0 )
{
obj->loadShaderSourceFromFile( fqFileName.c_str());
return true;

}
return false;
} 


struct RflCameraCallback : public osg::NodeCallback 
{
public:
RflCameraCallback(osg::Camera* mCamera):_mCamera(mCamera){}

virtual void operator()(osg::Node* node, osg::NodeVisitor* nv)
{
osg::Camera* rCamera = dynamic_cast (node);

osg::Matrix projectMatrix;
projectMatrix = _mCamera->getProjectionMatrix();
rCamera->setProjectionMatrix(projectMatrix);

osg::Vec3 eye, center, up;
_mCamera->getViewMatrixAsLookAt(eye, center, up);
rCamera->setViewMatrixAsLookAt(eye, center, up);

traverse(node, nv);
}   

osg::Camera* _mCamera;
};

osg::Geometry* createRegularSeaSurface()
{
osg::Geometry* seaGeom = new osg::Geometry;
seaGeom->setSupportsDisplayList(false); 

osg::Vec3Array* vertices = new osg::Vec3Array; //坐标顶点指针
osg::UIntArray* indeces = new osg::UIntArray; //坐标顶点索引指针
seaGeom->setVertexArray( vertices);

vertices->push_back(osg::Vec3(-40.0, -40.0, 0.0));
vertices->push_back(osg::Vec3(40.0, -40.0, 0.0));
vertices->push_back(osg::Vec3(40.0, 40.0, 0.0));
vertices->push_back(osg::Vec3(-40.0, 40.0, 0.0));

osg::Vec4Array* colors = new osg::Vec4Array;
seaGeom->setColorArray( colors );
seaGeom->setColorBinding( osg::Geometry::BIND_OVERALL );
colors->push_back( osg::Vec4( 1.f, 1.f, 1.f, 1.f ) );

seaGeom->addPrimitiveSet(new osg::DrawArrays(osg::PrimitiveSet::QUADS, 
0, 4));

return seaGeom;
}

osg::Node* createPreRenderSubGraph(osgViewer::Viewer* viewer, osg::Node* 
subgraph)
{
unsigned int tex_width = 512;
unsigned int tex_height = 512; 

// create a group to contain the flag and the pre rendering camera.
osg::Group* parent = new osg::Group;

// texture to render to and to use for rendering of flag.
osg::Texture2D* texture2D = new osg::Texture2D;
texture2D->setTextureSize(tex_width, tex_height);
texture2D->setInternalFormat(GL_RGBA);
texture2D->setFilter(osg::Texture2D::MIN_FILTER,osg::Texture2D::LINEAR);
texture2D->setFilter(osg::Texture2D::MAG_FILTER,osg::Texture2D::LINEAR);
osg::Texture* texture = texture2D;

// first create the geometry of the flag of which to view.
{ 
osg::Geometry* polyGeom = createRegularSeaSurface();

osg::StateSet* seaStateSet = new osg::StateSet;
seaStateSet->setTextureAttributeAndModes(0, texture);

//set shaders for RTT
osg::Program* seaProgramObject = new osg::Program;
{
osg::Shader* seaVertexObject = new osg::Shader( 
osg::Shader::VERTEX );
osg::Shader* seaFragmentObject = new osg::Shader( 
osg::Shader::FRAGMENT );

seaProgramObject->addShader( seaVertexObject);
seaProgramObject->addShader( seaFragmentObject);

loadShaderSource( seaVertexObject, "shaders/sea.vs" );
loadShaderSource( seaFragmentObject, "shaders/sea.fg" );

seaStateSet->addUniform(new osg::Uniform("rflTex", 0));
seaStateSet->setAttributeAndModes(seaProgramObject);
}   

polyGeom->setStateSet(seaStateSet);

osg::Geode* geode = new osg::Geode();
geode->addDrawable(polyGeom);

parent->addChild(geode);
}


// then create the camera node to do the render to texture
{
osg::Camera* rflCamera = new osg::Camera;

osg::Camera* mCamera = viewer->getCamera();
osg::Matrix projectMatrix;
projectMatrix = mCamera->getProjectionMatrix();
rflCamera->setProjectionMatrix(projectMatrix);

osg::Vec3 eye, center, up;
mCamera->getViewMatrixAsLookAt(eye, center, up);
rflCamera->setViewMatrixAsLookAt(eye, center, up);

rflCamera->setClearColor(osg::Vec4(1, 1, 1, 1)); 
rflCamera->set

[osg-users] Picking primitive subset

[Andrew Cunningham]

Hi,
I have a geometry that is represented by perhaps 500K triangle and/or quad 
primitives.

During user interaction, I need to pick ( using a selection rectangle) a 
significant subset ( say 10K) of these primitives and "highlight" them ( simply 
turning the picked primitives wireframe would do).


Any suggestions on how to do this efficiently? I have OSG picking working great 
with osg::Node objects but am a bit unsure of how to pick a subset of primitive 
QUADS/TRIS from a single geometry.

Thank you!

Cheers,
Andrew

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=13297#13297





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

[osg-users] Set fog in the canera StateSet

[Cristina Paponi]

Hi,

Could you please help me with the following problem. In my scene I have 2 
cameras one for day and one for thermo.
Because the fog will appear different in day and thermo, I tried to assign the 
fog to the camera's StateSet.
When I try to set the fog attribute to the camera StateSet there is no effect, 
but if I set the fog to the root of the scene's StateSet everything is fine.
Is it possible to set the fog in the camera ?

Thank you!

Cheers,
Cristina

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=13293#13293





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Problems using setResizeNonPowerOfTwoHint(false);

[Tomlinson, Gordon]

Hi Robert

Ok we will give it a go and get back to you 


Gordon
Product Manager 3d
__
Gordon Tomlinson
Email  : gtomlinson @ overwatch.textron.com
__


-Original Message-
From: osg-users-boun...@lists.openscenegraph.org 
[mailto:osg-users-boun...@lists.openscenegraph.org] On Behalf Of Robert Osfield
Sent: Monday, June 01, 2009 12:50 PM
To: OpenSceneGraph Users
Subject: Re: [osg-users] Problems using setResizeNonPowerOfTwoHint(false);

Hi Gordon,

I've just tracked down the original posts from Mark and have looked at his 
sample and suggested fix.  The fix hasn't been merged, nor a variation on it.  
I vaguely remember the thread, but not any resolution, it might be that I was 
swept away by other work so didn't chase it up.

I've just tried to reproduce the problem using the Sample.cpp but unfortunately 
I can't reproduce the problem on my ATI based system as it does have full 
support for non power of two with mipmapping.  I've followed the logic of the 
related generate mipmap code and can see how it would fail, and why Mark's 
suggest should address this failure.

The failure looks to have been due to introduction of more "advanced"
mipmap generation support, which probably worked in some usage combinations but 
not all.

I have taken the essence of Mark's fixed and applied to Texture2D.cpp, could 
you test this as I can't reproduce the problem to know whether it's been fixed 
or not.

Robert.

On Mon, Jun 1, 2009 at 2:39 PM, Tomlinson, Gordon 
 wrote:
> Hi
>
> Were having problems with textures that are non power of 2 or power 2 
> if we use   m_texture->setResizeNonPowerOfTwoHint(false);
> we get no texture
>
> The engineer who spotted this says this post 
> http://www.mail-archive.com/osg-users@lists.openscenegraph.org/msg1520
> 6.html had a fix but looks like it never made it submission or was 
> maybe rejects , does any one elsehave this issue,  was this fix  ever 
> applied  ?
>
> Fails in 2.8
> Works in 2.3/4
>
>
>
>
>
>
>
>
>
> Gordon
> Product Manager 3d
> __
> Gordon Tomlinson
> Email  : gtomlinso...@ overwatch.textron.com 
> __
> (C): (+1) 571-265-2612
> (W): (+1) 703-437-7651
>
> "Self defence is not a function of learning tricks but is a function 
> of how quickly and intensely one can arouse one's instinct for 
> survival"
> - Master Tambo Tetsura
>
>
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.
> org
>
>
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Help. KeyboardEventHandler and native keyboard layout bug in Linux

[Melchior FRANZ]

Passed the FlightGear test without problems.

m.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Problems using setResizeNonPowerOfTwoHint(false);

[Robert Osfield]

Hi Gordon,

I've just tracked down the original posts from Mark and have looked at
his sample and suggested fix.  The fix hasn't been merged, nor a
variation on it.  I vaguely remember the thread, but not any
resolution, it might be that I was swept away by other work so didn't
chase it up.

I've just tried to reproduce the problem using the Sample.cpp but
unfortunately I can't reproduce the problem on my ATI based system as
it does have full support for non power of two with mipmapping.  I've
followed the logic of the related generate mipmap code and can see how
it would fail, and why Mark's suggest should address this failure.

The failure looks to have been due to introduction of more "advanced"
mipmap generation support, which probably worked in some usage
combinations but not all.

I have taken the essence of Mark's fixed and applied to Texture2D.cpp,
could you test this as I can't reproduce the problem to know whether
it's been fixed or not.

Robert.

On Mon, Jun 1, 2009 at 2:39 PM, Tomlinson, Gordon
 wrote:
> Hi
>
> Were having problems with textures that are non power of 2 or power 2 if
> we use   m_texture->setResizeNonPowerOfTwoHint(false);
> we get no texture
>
> The engineer who spotted this says this post
> http://www.mail-archive.com/osg-users@lists.openscenegraph.org/msg15206.html
> had a fix but looks like it never made it submission or was maybe rejects ,
> does any one elsehave this issue,  was this fix  ever applied  ?
>
> Fails in 2.8
> Works in 2.3/4
>
>
>
>
>
>
>
>
>
> Gordon
> Product Manager 3d
> __
> Gordon Tomlinson
> Email  : gtomlinso...@ overwatch.textron.com
> __
> (C): (+1) 571-265-2612
> (W): (+1) 703-437-7651
>
> "Self defence is not a function of learning tricks
> but is a function of how quickly and intensely one
> can arouse one's instinct for survival"
> - Master Tambo Tetsura
>
>
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
>
/* -*-c++-*- OpenSceneGraph - Copyright (C) 1998-2006 Robert Osfield 
 *
 * This library is open source and may be redistributed and/or modified under  
 * the terms of the OpenSceneGraph Public License (OSGPL) version 0.0 or 
 * (at your option) any later version.  The full license is in LICENSE file
 * included with this distribution, and on the openscenegraph.org website.
 * 
 * This library is distributed in the hope that it will be useful,
 * but WITHOUT ANY WARRANTY; without even the implied warranty of
 * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the 
 * OpenSceneGraph Public License for more details.
*/

#include 
#include 
#include 
#include 
#include 
#include 

using namespace osg;

Texture2D::Texture2D():
_textureWidth(0),
_textureHeight(0),
_numMipmapLevels(0)
{
setUseHardwareMipMapGeneration(true);
}

Texture2D::Texture2D(Image* image):
_textureWidth(0),
_textureHeight(0),
_numMipmapLevels(0)
{
setUseHardwareMipMapGeneration(true);
setImage(image);
}

Texture2D::Texture2D(const Texture2D& text,const CopyOp& copyop):
Texture(text,copyop),
_image(copyop(text._image.get())),
_textureWidth(text._textureWidth),
_textureHeight(text._textureHeight),
_numMipmapLevels(text._numMipmapLevels),
_subloadCallback(text._subloadCallback)
{
}

Texture2D::~Texture2D()
{
}

int Texture2D::compare(const StateAttribute& sa) const
{
// check the types are equal and then create the rhs variable
// used by the COMPARE_StateAttribute_Parameter macro's below.
COMPARE_StateAttribute_Types(Texture2D,sa)

if (_image!=rhs._image) // smart pointer comparison.
{
if (_image.valid())
{
if (rhs._image.valid())
{
int result = _image->compare(*rhs._image);
if (result!=0) return result;
}
else
{
return 1; // valid lhs._image is greater than null. 
}
}
else if (rhs._image.valid()) 
{
return -1; // valid rhs._image is greater than null. 
}
}

if (!_image && !rhs._image)
{
// no image attached to either Texture2D
// but could these textures already be downloaded?
// check the _textureObjectBuffer to see if they have been
// downloaded

int result = compareTextureObjects(rhs);
if (result!=0) return result;
}

int result = compareTexture(rhs);
if (result!=0) return result;

// compare each parameter in turn against the rhs.
#if 1
if (_textureWidth != 0 && rhs._textureWidth != 0)
{
COMPARE_StateAttribute_Parameter(_textureWidth)
}
if (_textureHeight != 0 && 

Re: [osg-users] Help. KeyboardEventHandler and native keyboard layout bug in Linux

[Robert Osfield]

On Mon, Jun 1, 2009 at 5:03 PM, Melchior FRANZ  wrote:
> * Robert Osfield -- Monday 01 June 2009:
>> The Delete returning a osgGA::GUIEventAdapter::KEY_Delete is appropriate 
>> though.
>
> Whoops, sorry. Looked suspicious, and there's no way to test that in 
> osgkeyboard.

osgkeyboard doesn't report the "Delete" key being pressed when I press
it so it does look to be working, at least on my UK Keyboard + Kubuntu
9.04.

> Have yet to link FlightGear with the new version, but ...
>
>> Could you try the attached GraphicsWindowX11.cpp.
>
> ... so far it looks good! That's with an US-keyboard. Now trying FlightGear 
> ...

Fingers and toes crossed :-)

Robert.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Help. KeyboardEventHandler and native keyboard layout bug in Linux

[Melchior FRANZ]

Hi,

* Robert Osfield -- Monday 01 June 2009:
> The Delete returning a osgGA::GUIEventAdapter::KEY_Delete is appropriate 
> though.

Whoops, sorry. Looked suspicious, and there's no way to test that in 
osgkeyboard.
Have yet to link FlightGear with the new version, but ...



> Could you try the attached GraphicsWindowX11.cpp.

... so far it looks good! That's with an US-keyboard. Now trying FlightGear ...

m.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] manual delete object

[Robert Osfield]

On Mon, Jun 1, 2009 at 4:39 PM, Rabbi Robinson  wrote:
> Hi,
> Thanks, if later I reference the node from a group, will the reference count 
> be increased for the node?
>
> {
> osg::ref_ptr node = new Node;
> osg::ref_ptr group = new Group;
> group->addChild(node);
> }
>
> The reference count of node should be one outside the scope. Is it right that 
> somehow group->addChild(node) increases the reference count of node?

I won't answer this directly - an exercise for the reader...

The hint I'll give is that Group uses osg::ref_ptr
internally so when you add a node it
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] manual delete object

[Rabbi Robinson]

Hi,
Thanks, if later I reference the node from a group, will the reference count be 
increased for the node?

{
osg::ref_ptr node = new Node;
osg::ref_ptr group = new Group;
group->addChild(node);
}

The reference count of node should be one outside the scope. Is it right that 
somehow group->addChild(node) increases the reference count of node?


Thank you!

Cheers,
Rabbi

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=13284#13284





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Help. KeyboardEventHandler and native keyboard layout bug in Linux

[Melchior FRANZ]

* Robert Osfield -- Monday 01 June 2009:
> see if things are now working correctly in osgkeyboard

Nope.

Ctrl-a returns 0004-0061 again (an 'a'), instead of 0004-0001,
and Delete returns -.

m.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] smooth angle on normal calculation

[Robert Osfield]

On Mon, Jun 1, 2009 at 4:01 PM, Matthias Asselborn
 wrote:
> in many CAD progs,
> is there an option to recalculate Normals with an given angle.
> Especially for smoothing.

Are you talking about assigning a maximum crease angle that you don't
smooth over, but instead duplicate the vertices and normals and then
create a hard edge?

You *really* need to learn how to be specific when specifying what you
want, you really shouldn't expect others to get inside your head to
work this stuff out.  Please re-read your texts to see how meaningless
talking about angles is.

>
> In OpenSG for example exists the
> methode: calcVertexNormals(geo, deg2rad(30))
>
> therefore my question if this is also
> implemented in osg yet.

No there isn't an implementation.

> Or how can i implement it?

You find yourself a editor and compiler and do it.

Robert.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Website not reachable from france and austria

[Chris 'Xenon' Hanson]

Jose Luis Hidalgo wrote:
> Hi All,
>We've had a problem with the host of our OSG virtual machine, looks
> like we are having problems with the vmware that we are currently
> using. I'm considering the possibility to move to another
> virtualization technology , like libvirt, does any of you have insight
> into wich one is better?

  FWIW, I've been running Xen as my reactualizations layer for a while and have 
been happy
with it. I experimented with VirtualBox and VMWare (and qemu, but it's not what 
I'd really
consider a serious virtualization contender).

  I know KVM is popular with the Linux kernel crowd, but it didn't seem as 
mature, and to
me it seemed more like a "desktop" virtualization solution than a
run-lots-of-VMs-on-a-headless-server solution. I could be wrong though.

  Xen is mature and stable, and is used by Amazon's EC computing cloud to run 
tens of
thousands of virtual machines, so I figured that was a good endorsement. Xen 
can be faster
than other VM solutions if you run an OS that can be made Xen-aware (like 
Linux) and
cooperative. If you choose to pursue Xen, I can offer a few tips.

  Thanks for your hard work keeping the site running.

> Cheers,
>Jose-Luis.

-- 
Chris 'Xenon' Hanson, omo sanza lettere  Xenon AlphaPixel.com
PixelSense Landsat processing now available! http://www.alphapixel.com/demos/
"There is no Truth. There is only Perception. To Perceive is to Exist." - Xen
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] manual delete object

[Robert Osfield]

Hi Rabbi,

The destructor of most OSG class is deliberately made protected so
your can't delete it directly using delete, it also prevents the class
from being created on the stack.

Why?  This is a C++ programming trick that can help prevent misue of
C++ classes that are reference counted, and the OSG uses reference
almost everywhere for it's memory management of scene graph classes so
it's crucial that users use reference counting rather than try and mix
and match objects memory management.

The final answer to your question, how do you delete... well you don't
you leave it up to smart pointers and reference counting to do the
job.  You simple do:

  {
  osg::ref_ptr node = new Node; // create node on stack and
take a reference to it.
  } // ref_ptr goes out of scope and decrements the reference count,
and if it goes to 0, then it's deleted.

Robert.

On Mon, Jun 1, 2009 at 3:54 PM, Rabbi Robinson  wrote:
> Hi,
>
> When I tried
>
> Node* node = new Node;
> delete node;
>
> there is a compiler error saying destructor protected. How can I delete node 
> that I am sure I no longer use.
>
> Thank you!
>
> Cheers,
> Rabbi
>
> --
> Read this topic online here:
> http://forum.openscenegraph.org/viewtopic.php?p=13275#13275
>
>
>
>
>
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] smooth angle on normal calculation

[Matthias Asselborn]

in many CAD progs, 
is there an option to recalculate Normals with an given angle.
Especially for smoothing. 

In OpenSG for example exists the 
methode: calcVertexNormals(geo, deg2rad(30)) 

therefore my question if this is also 
implemented in osg yet.

Or how can i implement it?

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=13277#13277





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Help. KeyboardEventHandler and native keyboard layout bug in Linux

[Maxim Gammer]

OK.

"ABCD" (Russian) and "ABCD" (USA) result ..


KeyPress event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 4190830, (50,-17), root:(746,754),
state 0x2012, keycode 38 (keysym 0x6e6, Cyrillic_EF), same_screen YES,
XLookupString gives 2 bytes: (d0 a4) "Ф"
XmbLookupString gives 2 bytes: (d0 a4) "Ф"
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 4190942, (50,-17), root:(746,754),
state 0x2012, keycode 38 (keysym 0x6e6, Cyrillic_EF), same_screen YES,
XLookupString gives 2 bytes: (d0 a4) "Ф"
XFilterEvent returns: False

KeyPress event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 4191095, (50,-17), root:(746,754),
state 0x2012, keycode 56 (keysym 0x6e9, Cyrillic_I), same_screen YES,
XLookupString gives 2 bytes: (d0 98) "И"
XmbLookupString gives 2 bytes: (d0 98) "И"
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 4191194, (50,-17), root:(746,754),
state 0x2012, keycode 56 (keysym 0x6e9, Cyrillic_I), same_screen YES,
XLookupString gives 2 bytes: (d0 98) "И"
XFilterEvent returns: False

KeyPress event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 4191410, (50,-17), root:(746,754),
state 0x2012, keycode 54 (keysym 0x6f3, Cyrillic_ES), same_screen YES,
XLookupString gives 2 bytes: (d0 a1) "С"
XmbLookupString gives 2 bytes: (d0 a1) "С"
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 4191543, (50,-17), root:(746,754),
state 0x2012, keycode 54 (keysym 0x6f3, Cyrillic_ES), same_screen YES,
XLookupString gives 2 bytes: (d0 a1) "С"
XFilterEvent returns: False

KeyPress event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 4191744, (50,-17), root:(746,754),
state 0x2012, keycode 40 (keysym 0x6f7, Cyrillic_VE), same_screen YES,
XLookupString gives 2 bytes: (d0 92) "В"
XmbLookupString gives 2 bytes: (d0 92) "В"
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 4191855, (50,-17), root:(746,754),
state 0x2012, keycode 40 (keysym 0x6f7, Cyrillic_VE), same_screen YES,
XLookupString gives 2 bytes: (d0 92) "В"
XFilterEvent returns: False

KeyPress event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 4198549, (58,-144), root:(754,627),
state 0x2012, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyPress event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 4198768, (58,-144), root:(754,627),
state 0x2016, keycode 50 (keysym 0xfe0a, ISO_Prev_Group), same_screen YES,
XKeysymToKeycode returns keycode: 37
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 4198949, (58,-144), root:(754,627),
state 0x16, keycode 50 (keysym 0xfe0a, ISO_Prev_Group), same_screen YES,
XKeysymToKeycode returns keycode: 37
XLookupString gives 0 bytes:
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 4198967, (58,-144), root:(754,627),
state 0x16, keycode 37 (keysym 0xffe3, Control_L), same_screen YES,
XLookupString gives 0 bytes:
XFilterEvent returns: False

KeyPress event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 4202905, (46,-15), root:(742,756),
state 0x12, keycode 38 (keysym 0x41, A), same_screen YES,
XLookupString gives 1 bytes: (41) "A"
XmbLookupString gives 1 bytes: (41) "A"
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 4203037, (46,-15), root:(742,756),
state 0x12, keycode 38 (keysym 0x41, A), same_screen YES,
XLookupString gives 1 bytes: (41) "A"
XFilterEvent returns: False

KeyPress event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 4203113, (46,-15), root:(742,756),
state 0x12, keycode 56 (keysym 0x42, B), same_screen YES,
XLookupString gives 1 bytes: (42) "B"
XmbLookupString gives 1 bytes: (42) "B"
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 4203209, (46,-15), root:(742,756),
state 0x12, keycode 56 (keysym 0x42, B), same_screen YES,
XLookupString gives 1 bytes: (42) "B"
XFilterEvent returns: False

KeyPress event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 4203279, (46,-15), root:(742,756),
state 0x12, keycode 54 (keysym 

Re: [osg-users] manual delete object

[Tomlinson, Gordon]

 
Nodes are derived from Object which is refcounted thus the destructor is
not directly accessible

You can use 

node->unref();
Node = NULL;

Gordon
Product Manager 3d
__
Gordon Tomlinson
Email  : gtomlinson @ overwatch.textron.com
__


-Original Message-
From: osg-users-boun...@lists.openscenegraph.org
[mailto:osg-users-boun...@lists.openscenegraph.org] On Behalf Of Rabbi
Robinson
Sent: Monday, June 01, 2009 10:55 AM
To: osg-users@lists.openscenegraph.org
Subject: [osg-users] manual delete object

Hi,

When I tried

Node* node = new Node;
delete node;

there is a compiler error saying destructor protected. How can I delete
node that I am sure I no longer use.

Thank you!

Cheers,
Rabbi

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=13275#13275





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.or
g
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

[osg-users] manual delete object

[Rabbi Robinson]

Hi,

When I tried

Node* node = new Node;
delete node;

there is a compiler error saying destructor protected. How can I delete node 
that I am sure I no longer use.

Thank you!

Cheers,
Rabbi

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=13275#13275





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] osg::ref_ptr<> used anymore

[Rabbi Robinson]

Hi,

Ok, I started this thread, so I claim to have the right for the last words.

I have used boost before, it looks like a pretty well maintained library. I 
used it because I was working on my coworker's code and in our case, he only 
used the file separator ("\" vs "/") from boost. For that it probably took more 
that 45 minutes to build boost in VC++, which include all other things such as 
matrix manipulation, threads, signal, BLAS that we did not use.

I guess some people feel it heavy in a sense that you can't download and build 
just the components you need(if there is a way to do it, I don't know and 
apologize for my ignorance). Instead, everything comes in an all-inclusive 
package. For small or dedicated project where resource and performance count, 
it dose not look appealing.

Boost can be trusted as well tested library. Sometimes being "big" and 
"all-inclusive" is not necessarily a good thing. For example, there is BLAS in 
boost, but there are other free libraries around that dose the same thing (GSL, 
ITK or even IPP in linux). As a result users have a choice of the BLAS from 
boost, which is a component from an all-inclusive library, or they can select 
GSL, ITK or IPP, which specializes just in scientific computation and dose not 
offer more than that. Performance wise, I think boost still need to prove 
itself that it can compete with those dedicated libraries.

At this point, it's totally personal preference and project needs. For me, I 
tend to use the libraries that dose only one thing well and leave small memory 
footprints. I like it that way because I have the freedom to use that libraries 
for other purposes, so it's more flexible that way.

Thank you!

Cheers,
Rabbi

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=13274#13274





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Help. KeyboardEventHandler and native keyboard layout bug in Linux

[Robert Osfield]

Hi Maxim,

Could you now do the same test with caps lock on, so the 'ABCD'.

W.r.t the XLookupString result strings, do these look sensible?

Robert.

2009/6/1 Maxim Gammer :
> Hi, Robert
>
> ...xev result for "abcd" (Russian):
>
> KeyPress event, serial 34, synthetic NO, window 0x381,
>    root 0x13c, subw 0x0, time 3487419, (68,-21), root:(764,750),
>    state 0x2010, keycode 38 (keysym 0x6c6, Cyrillic_ef), same_screen YES,
>    XLookupString gives 2 bytes: (d1 84) "ф"
>    XmbLookupString gives 2 bytes: (d1 84) "ф"
>    XFilterEvent returns: False
>
> KeyRelease event, serial 34, synthetic NO, window 0x381,
>    root 0x13c, subw 0x0, time 3487518, (68,-21), root:(764,750),
>    state 0x2010, keycode 38 (keysym 0x6c6, Cyrillic_ef), same_screen YES,
>    XLookupString gives 2 bytes: (d1 84) "ф"
>    XFilterEvent returns: False
>
> KeyPress event, serial 34, synthetic NO, window 0x381,
>    root 0x13c, subw 0x0, time 3489948, (68,-21), root:(764,750),
>    state 0x2010, keycode 56 (keysym 0x6c9, Cyrillic_i), same_screen YES,
>    XLookupString gives 2 bytes: (d0 b8) "и"
>    XmbLookupString gives 2 bytes: (d0 b8) "и"
>    XFilterEvent returns: False
>
> KeyRelease event, serial 34, synthetic NO, window 0x381,
>    root 0x13c, subw 0x0, time 3490056, (68,-21), root:(764,750),
>    state 0x2010, keycode 56 (keysym 0x6c9, Cyrillic_i), same_screen YES,
>    XLookupString gives 2 bytes: (d0 b8) "и"
>    XFilterEvent returns: False
>
> KeyPress event, serial 34, synthetic NO, window 0x381,
>    root 0x13c, subw 0x0, time 3490683, (68,-21), root:(764,750),
>    state 0x2010, keycode 54 (keysym 0x6d3, Cyrillic_es), same_screen YES,
>    XLookupString gives 2 bytes: (d1 81) "с"
>    XmbLookupString gives 2 bytes: (d1 81) "с"
>    XFilterEvent returns: False
>
> KeyRelease event, serial 34, synthetic NO, window 0x381,
>    root 0x13c, subw 0x0, time 3490804, (68,-21), root:(764,750),
>    state 0x2010, keycode 54 (keysym 0x6d3, Cyrillic_es), same_screen YES,
>    XLookupString gives 2 bytes: (d1 81) "с"
>    XFilterEvent returns: False
>
> KeyPress event, serial 34, synthetic NO, window 0x381,
>    root 0x13c, subw 0x0, time 3491437, (68,-21), root:(764,750),
>    state 0x2010, keycode 40 (keysym 0x6d7, Cyrillic_ve), same_screen YES,
>    XLookupString gives 2 bytes: (d0 b2) "в"
>    XmbLookupString gives 2 bytes: (d0 b2) "в"
>    XFilterEvent returns: False
>
> KeyRelease event, serial 34, synthetic NO, window 0x381,
>    root 0x13c, subw 0x0, time 3491551, (68,-21), root:(764,750),
>    state 0x2010, keycode 40 (keysym 0x6d7, Cyrillic_ve), same_screen YES,
>    XLookupString gives 2 bytes: (d0 b2) "в"
>    XFilterEvent returns: False
>
>
> 2009/6/1 Robert Osfield :
>> HI Maxim,
>>
>> I'm afraid what you've sent is rather difficult to follow and
>> seemingly inconsitent with your previous post. Could you post the
>> results in sections with a heading of what follows.
>>
>> In searching the web on XLookupString and Russian I came across the
>> little test application xev that outputs the keyboard symbol and
>> XLookupString results, could you have a look at what results you get
>> for the Russian vs USA with this.
>>
>> Thanks,
>> Robert.
>>
>> On Mon, Jun 1, 2009 at 3:35 PM, Maxim Gammer  wrote:
>>> Hi Robert,
>>>
>>> OK,
>>> "abcd" (USA), "ABCD" (USA), "abcd" (Russian), "ABCD" (Russian) .
>>>
>>>
>>>
>>>
>>> keyevent.keycode = 38, KeySym97, keySymbol97
>>>
>>> numChars = 1,97, 0
>>>
>>> keySymbol = 97
>>>
>>>
>>>
>>> keyevent.keycode = 38, KeySym97, keySymbol97
>>>
>>> numChars = 1,97, 0
>>>
>>> keySymbol = 97
>>>
>>>
>>>
>>> keyevent.keycode = 38, KeySym97, keySymbol97
>>>
>>> numChars = 1,97, 0
>>>
>>> keySymbol = 97
>>>
>>>
>>>
>>> keyevent.keycode = 56, KeySym98, keySymbol98
>>>
>>> numChars = 1,98, 0
>>>
>>> keySymbol = 98
>>>
>>>
>>>
>>> keyevent.keycode = 56, KeySym98, keySymbol98
>>>
>>> numChars = 1,98, 0
>>>
>>> keySymbol = 98
>>>
>>>
>>>
>>> keyevent.keycode = 56, KeySym98, keySymbol98
>>>
>>> numChars = 1,98, 0
>>>
>>> keySymbol = 98
>>>
>>>
>>>
>>> keyevent.keycode = 56, KeySym98, keySymbol98
>>>
>>> numChars = 1,98, 0
>>>
>>> keySymbol = 98
>>>
>>>
>>>
>>> keyevent.keycode = 56, KeySym98, keySymbol98
>>>
>>> numChars = 1,98, 0
>>>
>>> keySymbol = 98
>>>
>>>
>>>
>>> keyevent.keycode = 56, KeySym98, keySymbol98
>>>
>>> numChars = 1,98, 0
>>>
>>> keySymbol = 98
>>>
>>>
>>>
>>> keyevent.keycode = 56, KeySym98, keySymbol98
>>>
>>> numChars = 1,98, 0
>>>
>>> keySymbol = 98
>>>
>>>
>>>
>>> keyevent.keycode = 54, KeySym99, keySymbol99
>>>
>>> numChars = 1,99, 0
>>>
>>> keySymbol = 99
>>>
>>>
>>>
>>> keyevent.keycode = 54, KeySym99, keySymbol99
>>>
>>> numChars = 1,99, 0
>>>
>>> keySymbol = 99
>>>
>>>
>>>
>>> keyevent.keycode = 54, KeySym99, keySymbol99
>>>
>>> numChars = 1,99, 0
>>>
>>> keySymbol = 99
>>>
>>>
>>>
>>> keyevent.keycode = 40, KeySym100, keySymbol100
>>>
>>> numChars = 1,100, 0
>>>
>>> keySymbol = 100
>>>
>>>
>>>
>>> keyevent.keycode = 40, KeySym100, keySymbol

Re: [osg-users] Help. KeyboardEventHandler and native keyboard layout bug in Linux

[Maxim Gammer]

...xev result for "abcd" (USA):

KeyPress event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 3617200, (-262,-312), root:(434,459),
state 0x10, keycode 38 (keysym 0x61, a), same_screen YES,
XLookupString gives 1 bytes: (61) "a"
XmbLookupString gives 1 bytes: (61) "a"
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 3617306, (-262,-312), root:(434,459),
state 0x10, keycode 38 (keysym 0x61, a), same_screen YES,
XLookupString gives 1 bytes: (61) "a"
XFilterEvent returns: False

KeyPress event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 3618355, (-262,-312), root:(434,459),
state 0x10, keycode 56 (keysym 0x62, b), same_screen YES,
XLookupString gives 1 bytes: (62) "b"
XmbLookupString gives 1 bytes: (62) "b"
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 3618458, (-262,-312), root:(434,459),
state 0x10, keycode 56 (keysym 0x62, b), same_screen YES,
XLookupString gives 1 bytes: (62) "b"
XFilterEvent returns: False

KeyPress event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 3619216, (-262,-312), root:(434,459),
state 0x10, keycode 54 (keysym 0x63, c), same_screen YES,
XLookupString gives 1 bytes: (63) "c"
XmbLookupString gives 1 bytes: (63) "c"
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 3619330, (-262,-312), root:(434,459),
state 0x10, keycode 54 (keysym 0x63, c), same_screen YES,
XLookupString gives 1 bytes: (63) "c"
XFilterEvent returns: False

KeyPress event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 3619871, (-262,-312), root:(434,459),
state 0x10, keycode 40 (keysym 0x64, d), same_screen YES,
XLookupString gives 1 bytes: (64) "d"
XmbLookupString gives 1 bytes: (64) "d"
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 3619979, (-262,-312), root:(434,459),
state 0x10, keycode 40 (keysym 0x64, d), same_screen YES,
XLookupString gives 1 bytes: (64) "d"
XFilterEvent returns: False


1 июня 2009 г. 20:47 пользователь Maxim Gammer  написал:
> Hi, Robert
>
> ...xev result for "abcd" (Russian):
>
> KeyPress event, serial 34, synthetic NO, window 0x381,
>    root 0x13c, subw 0x0, time 3487419, (68,-21), root:(764,750),
>    state 0x2010, keycode 38 (keysym 0x6c6, Cyrillic_ef), same_screen YES,
>    XLookupString gives 2 bytes: (d1 84) "ф"
>    XmbLookupString gives 2 bytes: (d1 84) "ф"
>    XFilterEvent returns: False
>
> KeyRelease event, serial 34, synthetic NO, window 0x381,
>    root 0x13c, subw 0x0, time 3487518, (68,-21), root:(764,750),
>    state 0x2010, keycode 38 (keysym 0x6c6, Cyrillic_ef), same_screen YES,
>    XLookupString gives 2 bytes: (d1 84) "ф"
>    XFilterEvent returns: False
>
> KeyPress event, serial 34, synthetic NO, window 0x381,
>    root 0x13c, subw 0x0, time 3489948, (68,-21), root:(764,750),
>    state 0x2010, keycode 56 (keysym 0x6c9, Cyrillic_i), same_screen YES,
>    XLookupString gives 2 bytes: (d0 b8) "и"
>    XmbLookupString gives 2 bytes: (d0 b8) "и"
>    XFilterEvent returns: False
>
> KeyRelease event, serial 34, synthetic NO, window 0x381,
>    root 0x13c, subw 0x0, time 3490056, (68,-21), root:(764,750),
>    state 0x2010, keycode 56 (keysym 0x6c9, Cyrillic_i), same_screen YES,
>    XLookupString gives 2 bytes: (d0 b8) "и"
>    XFilterEvent returns: False
>
> KeyPress event, serial 34, synthetic NO, window 0x381,
>    root 0x13c, subw 0x0, time 3490683, (68,-21), root:(764,750),
>    state 0x2010, keycode 54 (keysym 0x6d3, Cyrillic_es), same_screen YES,
>    XLookupString gives 2 bytes: (d1 81) "с"
>    XmbLookupString gives 2 bytes: (d1 81) "с"
>    XFilterEvent returns: False
>
> KeyRelease event, serial 34, synthetic NO, window 0x381,
>    root 0x13c, subw 0x0, time 3490804, (68,-21), root:(764,750),
>    state 0x2010, keycode 54 (keysym 0x6d3, Cyrillic_es), same_screen YES,
>    XLookupString gives 2 bytes: (d1 81) "с"
>    XFilterEvent returns: False
>
> KeyPress event, serial 34, synthetic NO, window 0x381,
>    root 0x13c, subw 0x0, time 3491437, (68,-21), root:(764,750),
>    state 0x2010, keycode 40 (keysym 0x6d7, Cyrillic_ve), same_screen YES,
>    XLookupString gives 2 bytes: (d0 b2) "в"
>    XmbLookupString gives 2 bytes: (d0 b2) "в"
>    XFilterEvent returns: False
>
> KeyRelease event, serial 34, synthetic NO, window 0x381,
>    root 0x13c, subw 0x0, time 3491551, (68,-21), root:(764,750),
>    state 0x2010, keycode 40 (keysym 0x6d7, Cyrillic_ve), same_screen YES,
>    XLookupString gives 2 bytes: (d0 b2) "в"
>    XFilterEvent returns: False
>
>
> 2009/6/1 Robert Osfield :
>> HI Maxim,
>>
>> I'm afraid what you've

Re: [osg-users] Help. KeyboardEventHandler and native keyboard layout bug in Linux

[Maxim Gammer]

Hi, Robert

...xev result for "abcd" (Russian):

KeyPress event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 3487419, (68,-21), root:(764,750),
state 0x2010, keycode 38 (keysym 0x6c6, Cyrillic_ef), same_screen YES,
XLookupString gives 2 bytes: (d1 84) "ф"
XmbLookupString gives 2 bytes: (d1 84) "ф"
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 3487518, (68,-21), root:(764,750),
state 0x2010, keycode 38 (keysym 0x6c6, Cyrillic_ef), same_screen YES,
XLookupString gives 2 bytes: (d1 84) "ф"
XFilterEvent returns: False

KeyPress event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 3489948, (68,-21), root:(764,750),
state 0x2010, keycode 56 (keysym 0x6c9, Cyrillic_i), same_screen YES,
XLookupString gives 2 bytes: (d0 b8) "и"
XmbLookupString gives 2 bytes: (d0 b8) "и"
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 3490056, (68,-21), root:(764,750),
state 0x2010, keycode 56 (keysym 0x6c9, Cyrillic_i), same_screen YES,
XLookupString gives 2 bytes: (d0 b8) "и"
XFilterEvent returns: False

KeyPress event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 3490683, (68,-21), root:(764,750),
state 0x2010, keycode 54 (keysym 0x6d3, Cyrillic_es), same_screen YES,
XLookupString gives 2 bytes: (d1 81) "с"
XmbLookupString gives 2 bytes: (d1 81) "с"
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 3490804, (68,-21), root:(764,750),
state 0x2010, keycode 54 (keysym 0x6d3, Cyrillic_es), same_screen YES,
XLookupString gives 2 bytes: (d1 81) "с"
XFilterEvent returns: False

KeyPress event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 3491437, (68,-21), root:(764,750),
state 0x2010, keycode 40 (keysym 0x6d7, Cyrillic_ve), same_screen YES,
XLookupString gives 2 bytes: (d0 b2) "в"
XmbLookupString gives 2 bytes: (d0 b2) "в"
XFilterEvent returns: False

KeyRelease event, serial 34, synthetic NO, window 0x381,
root 0x13c, subw 0x0, time 3491551, (68,-21), root:(764,750),
state 0x2010, keycode 40 (keysym 0x6d7, Cyrillic_ve), same_screen YES,
XLookupString gives 2 bytes: (d0 b2) "в"
XFilterEvent returns: False


2009/6/1 Robert Osfield :
> HI Maxim,
>
> I'm afraid what you've sent is rather difficult to follow and
> seemingly inconsitent with your previous post. Could you post the
> results in sections with a heading of what follows.
>
> In searching the web on XLookupString and Russian I came across the
> little test application xev that outputs the keyboard symbol and
> XLookupString results, could you have a look at what results you get
> for the Russian vs USA with this.
>
> Thanks,
> Robert.
>
> On Mon, Jun 1, 2009 at 3:35 PM, Maxim Gammer  wrote:
>> Hi Robert,
>>
>> OK,
>> "abcd" (USA), "ABCD" (USA), "abcd" (Russian), "ABCD" (Russian) .
>>
>>
>>
>>
>> keyevent.keycode = 38, KeySym97, keySymbol97
>>
>> numChars = 1,97, 0
>>
>> keySymbol = 97
>>
>>
>>
>> keyevent.keycode = 38, KeySym97, keySymbol97
>>
>> numChars = 1,97, 0
>>
>> keySymbol = 97
>>
>>
>>
>> keyevent.keycode = 38, KeySym97, keySymbol97
>>
>> numChars = 1,97, 0
>>
>> keySymbol = 97
>>
>>
>>
>> keyevent.keycode = 56, KeySym98, keySymbol98
>>
>> numChars = 1,98, 0
>>
>> keySymbol = 98
>>
>>
>>
>> keyevent.keycode = 56, KeySym98, keySymbol98
>>
>> numChars = 1,98, 0
>>
>> keySymbol = 98
>>
>>
>>
>> keyevent.keycode = 56, KeySym98, keySymbol98
>>
>> numChars = 1,98, 0
>>
>> keySymbol = 98
>>
>>
>>
>> keyevent.keycode = 56, KeySym98, keySymbol98
>>
>> numChars = 1,98, 0
>>
>> keySymbol = 98
>>
>>
>>
>> keyevent.keycode = 56, KeySym98, keySymbol98
>>
>> numChars = 1,98, 0
>>
>> keySymbol = 98
>>
>>
>>
>> keyevent.keycode = 56, KeySym98, keySymbol98
>>
>> numChars = 1,98, 0
>>
>> keySymbol = 98
>>
>>
>>
>> keyevent.keycode = 56, KeySym98, keySymbol98
>>
>> numChars = 1,98, 0
>>
>> keySymbol = 98
>>
>>
>>
>> keyevent.keycode = 54, KeySym99, keySymbol99
>>
>> numChars = 1,99, 0
>>
>> keySymbol = 99
>>
>>
>>
>> keyevent.keycode = 54, KeySym99, keySymbol99
>>
>> numChars = 1,99, 0
>>
>> keySymbol = 99
>>
>>
>>
>> keyevent.keycode = 54, KeySym99, keySymbol99
>>
>> numChars = 1,99, 0
>>
>> keySymbol = 99
>>
>>
>>
>> keyevent.keycode = 40, KeySym100, keySymbol100
>>
>> numChars = 1,100, 0
>>
>> keySymbol = 100
>>
>>
>>
>> keyevent.keycode = 40, KeySym100, keySymbol100
>>
>> numChars = 1,100, 0
>>
>> keySymbol = 100
>>
>>
>>
>> keyevent.keycode = 40, KeySym100, keySymbol100
>>
>> numChars = 1,100, 0
>>
>> keySymbol = 100
>>
>>
>>
>> keyevent.keycode = 40, KeySym100, keySymbol100
>>
>> numChars = 1,100, 0
>>
>> keySymbol = 100
>>
>>
>>
>> keyevent.keycode = 66, KeySym65509, keySymbol65509
>>
>> numChars = 0,0, 39
>>
>> keySymbol = 65509
>>

Re: [osg-users] Help. KeyboardEventHandler and native keyboard layout bug in Linux

[Robert Osfield]

Hi Melchior,


On Mon, Jun 1, 2009 at 3:14 PM, Melchior FRANZ  wrote:
> Seems to work OK here.

Thanks for the testing.  Once we get a combination that works OK for
standard usage and the Russian case I'll patch both svn/trunk and
OSG-2.8 branch.  Unfortunately this regression made it into 2.8.1 so
it looks like we may well have to make a 2.8.2 in the not too distant
future.

Robert.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Help. KeyboardEventHandler and native keyboard layout bug in Linux

[Robert Osfield]

HI Maxim,

I'm afraid what you've sent is rather difficult to follow and
seemingly inconsitent with your previous post. Could you post the
results in sections with a heading of what follows.

In searching the web on XLookupString and Russian I came across the
little test application xev that outputs the keyboard symbol and
XLookupString results, could you have a look at what results you get
for the Russian vs USA with this.

Thanks,
Robert.

On Mon, Jun 1, 2009 at 3:35 PM, Maxim Gammer  wrote:
> Hi Robert,
>
> OK,
> "abcd" (USA), "ABCD" (USA), "abcd" (Russian), "ABCD" (Russian) .
>
>
>
>
> keyevent.keycode = 38, KeySym97, keySymbol97
>
> numChars = 1,97, 0
>
> keySymbol = 97
>
>
>
> keyevent.keycode = 38, KeySym97, keySymbol97
>
> numChars = 1,97, 0
>
> keySymbol = 97
>
>
>
> keyevent.keycode = 38, KeySym97, keySymbol97
>
> numChars = 1,97, 0
>
> keySymbol = 97
>
>
>
> keyevent.keycode = 56, KeySym98, keySymbol98
>
> numChars = 1,98, 0
>
> keySymbol = 98
>
>
>
> keyevent.keycode = 56, KeySym98, keySymbol98
>
> numChars = 1,98, 0
>
> keySymbol = 98
>
>
>
> keyevent.keycode = 56, KeySym98, keySymbol98
>
> numChars = 1,98, 0
>
> keySymbol = 98
>
>
>
> keyevent.keycode = 56, KeySym98, keySymbol98
>
> numChars = 1,98, 0
>
> keySymbol = 98
>
>
>
> keyevent.keycode = 56, KeySym98, keySymbol98
>
> numChars = 1,98, 0
>
> keySymbol = 98
>
>
>
> keyevent.keycode = 56, KeySym98, keySymbol98
>
> numChars = 1,98, 0
>
> keySymbol = 98
>
>
>
> keyevent.keycode = 56, KeySym98, keySymbol98
>
> numChars = 1,98, 0
>
> keySymbol = 98
>
>
>
> keyevent.keycode = 54, KeySym99, keySymbol99
>
> numChars = 1,99, 0
>
> keySymbol = 99
>
>
>
> keyevent.keycode = 54, KeySym99, keySymbol99
>
> numChars = 1,99, 0
>
> keySymbol = 99
>
>
>
> keyevent.keycode = 54, KeySym99, keySymbol99
>
> numChars = 1,99, 0
>
> keySymbol = 99
>
>
>
> keyevent.keycode = 40, KeySym100, keySymbol100
>
> numChars = 1,100, 0
>
> keySymbol = 100
>
>
>
> keyevent.keycode = 40, KeySym100, keySymbol100
>
> numChars = 1,100, 0
>
> keySymbol = 100
>
>
>
> keyevent.keycode = 40, KeySym100, keySymbol100
>
> numChars = 1,100, 0
>
> keySymbol = 100
>
>
>
> keyevent.keycode = 40, KeySym100, keySymbol100
>
> numChars = 1,100, 0
>
> keySymbol = 100
>
>
>
> keyevent.keycode = 66, KeySym65509, keySymbol65509
>
> numChars = 0,0, 39
>
> keySymbol = 65509
>
>
>
> keyevent.keycode = 66, KeySym65509, keySymbol65509
>
> numChars = 0,0, 39
>
> keySymbol = 65509
>
>
>
> keyevent.keycode = 38, KeySym65, keySymbol65
>
> numChars = 1,65, 0
>
> keySymbol = 65
>
>
>
> keyevent.keycode = 38, KeySym65, keySymbol65
>
> numChars = 1,65, 0
>
> keySymbol = 65
>
>
>
> keyevent.keycode = 56, KeySym66, keySymbol66
>
> numChars = 1,66, 0
>
> keySymbol = 66
>
>
>
> keyevent.keycode = 56, KeySym66, keySymbol66
>
> numChars = 1,66, 0
>
> keySymbol = 66
>
>
>
> keyevent.keycode = 56, KeySym66, keySymbol66
>
> numChars = 1,66, 0
>
> keySymbol = 66
>
>
>
> keyevent.keycode = 54, KeySym67, keySymbol67
>
> numChars = 1,67, 0
>
> keySymbol = 67
>
>
>
> keyevent.keycode = 54, KeySym67, keySymbol67
>
> numChars = 1,67, 0
>
> keySymbol = 67
>
>
>
> keyevent.keycode = 40, KeySym68, keySymbol68
>
> numChars = 1,68, 0
> keySymbol = 68
>
>
> keyevent.keycode = 40, KeySym68, keySymbol68
>
> numChars = 1,68, 0
>
> keySymbol = 68
>
>
>
> keyevent.keycode = 40, KeySym68, keySymbol68
>
> numChars = 1,68, 0
>
> keySymbol = 68
>
>
>
> keyevent.keycode = 37, KeySym65507, keySymbol65507
>
> numChars = 0,0, 39
> keySymbol = 65507
>
>
> keyevent.keycode = 50, KeySym65034, keySymbol65034
>
> numChars = 0,0, 39
> keySymbol = 65034
>
>
> keyevent.keycode = 37, KeySym65507, keySymbol65507
>
> numChars = 0,0, 39
>
> keySymbol = 65507
>
>
>
> keyevent.keycode = 50, KeySym65505, keySymbol65505
>
> numChars = 0,0, 39
> keySymbol = 65505
>
>
> keyevent.keycode = 66, KeySym65509, keySymbol65509
> numChars = 0,0, 39
> keySymbol = 65509
>
>
> keyevent.keycode = 66, KeySym65509, keySymbol65509
>
> numChars = 0,0, 39
>
> keySymbol = 65509
>
>
>
> keyevent.keycode = 38, KeySym1734, keySymbol1734
>
> numChars = 0,0, 39
>
> keySymbol = 1734
>
>
>
> keyevent.keycode = 38, KeySym1734, keySymbol1734
>
> numChars = 0,0, 39
>
> keySymbol = 1734
>
>
>
> keyevent.keycode = 38, KeySym1734, keySymbol1734
>
> numChars = 0,0, 39
>
> keySymbol = 1734
>
>
>
> keyevent.keycode = 38, KeySym1734, keySymbol1734
>
> numChars = 0,0, 39
>
> keySymbol = 1734
>
>
>
> keyevent.keycode = 56, KeySym1737, keySymbol1737
>
> numChars = 0,0, 39
>
> keySymbol = 1737
>
>
>
> keyevent.keycode = 56, KeySym1737, keySymbol1737
>
> numChars = 0,0, 39
>
> keySymbol = 1737
>
>
>
> keyevent.keycode = 56, KeySym1737, keySymbol1737
>
> numChars = 0,0, 39
>
> keySymbol = 1737
>
>
>
> keyevent.keycode = 54, KeySym1747, keySymbol1747
>
> numChars = 0,0, 39
>
> keySymbol = 1747
>
>
>
> keyevent.keycode = 54, KeySym1747, keySymbol1747
>
> numChars = 0,0, 39
>
> keySymbol = 1747
>
>
>
> keyevent.keycode = 40, KeySym1751, keySymbol1751
>
> numChars = 0,0, 39
>
> keySymbol = 1751
>
>
>

Re: [osg-users] Help. KeyboardEventHandler and native keyboard layout bug in Linux

[Maxim Gammer]

Yes, work fine )

2009/6/1 Melchior FRANZ :
> Seems to work OK here.
>
> m.
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>



-- 
Maxim Gammer
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Help. KeyboardEventHandler and native keyboard layout bug in Linux

[Maxim Gammer]

Hi Robert,

OK,
"abcd" (USA), "ABCD" (USA), "abcd" (Russian), "ABCD" (Russian) .




keyevent.keycode = 38, KeySym97, keySymbol97

numChars = 1,97, 0

keySymbol = 97



keyevent.keycode = 38, KeySym97, keySymbol97

numChars = 1,97, 0

keySymbol = 97



keyevent.keycode = 38, KeySym97, keySymbol97

numChars = 1,97, 0

keySymbol = 97



keyevent.keycode = 56, KeySym98, keySymbol98

numChars = 1,98, 0

keySymbol = 98



keyevent.keycode = 56, KeySym98, keySymbol98

numChars = 1,98, 0

keySymbol = 98



keyevent.keycode = 56, KeySym98, keySymbol98

numChars = 1,98, 0

keySymbol = 98



keyevent.keycode = 56, KeySym98, keySymbol98

numChars = 1,98, 0

keySymbol = 98



keyevent.keycode = 56, KeySym98, keySymbol98

numChars = 1,98, 0

keySymbol = 98



keyevent.keycode = 56, KeySym98, keySymbol98

numChars = 1,98, 0

keySymbol = 98



keyevent.keycode = 56, KeySym98, keySymbol98

numChars = 1,98, 0

keySymbol = 98



keyevent.keycode = 54, KeySym99, keySymbol99

numChars = 1,99, 0

keySymbol = 99



keyevent.keycode = 54, KeySym99, keySymbol99

numChars = 1,99, 0

keySymbol = 99



keyevent.keycode = 54, KeySym99, keySymbol99

numChars = 1,99, 0

keySymbol = 99



keyevent.keycode = 40, KeySym100, keySymbol100

numChars = 1,100, 0

keySymbol = 100



keyevent.keycode = 40, KeySym100, keySymbol100

numChars = 1,100, 0

keySymbol = 100



keyevent.keycode = 40, KeySym100, keySymbol100

numChars = 1,100, 0

keySymbol = 100



keyevent.keycode = 40, KeySym100, keySymbol100

numChars = 1,100, 0

keySymbol = 100



keyevent.keycode = 66, KeySym65509, keySymbol65509

numChars = 0,0, 39

keySymbol = 65509



keyevent.keycode = 66, KeySym65509, keySymbol65509

numChars = 0,0, 39

keySymbol = 65509



keyevent.keycode = 38, KeySym65, keySymbol65

numChars = 1,65, 0

keySymbol = 65



keyevent.keycode = 38, KeySym65, keySymbol65

numChars = 1,65, 0

keySymbol = 65



keyevent.keycode = 56, KeySym66, keySymbol66

numChars = 1,66, 0

keySymbol = 66



keyevent.keycode = 56, KeySym66, keySymbol66

numChars = 1,66, 0

keySymbol = 66



keyevent.keycode = 56, KeySym66, keySymbol66

numChars = 1,66, 0

keySymbol = 66



keyevent.keycode = 54, KeySym67, keySymbol67

numChars = 1,67, 0

keySymbol = 67



keyevent.keycode = 54, KeySym67, keySymbol67

numChars = 1,67, 0

keySymbol = 67



keyevent.keycode = 40, KeySym68, keySymbol68

numChars = 1,68, 0
keySymbol = 68


keyevent.keycode = 40, KeySym68, keySymbol68

numChars = 1,68, 0

keySymbol = 68



keyevent.keycode = 40, KeySym68, keySymbol68

numChars = 1,68, 0

keySymbol = 68



keyevent.keycode = 37, KeySym65507, keySymbol65507

numChars = 0,0, 39
keySymbol = 65507


keyevent.keycode = 50, KeySym65034, keySymbol65034

numChars = 0,0, 39
keySymbol = 65034


keyevent.keycode = 37, KeySym65507, keySymbol65507

numChars = 0,0, 39

keySymbol = 65507



keyevent.keycode = 50, KeySym65505, keySymbol65505

numChars = 0,0, 39
keySymbol = 65505


keyevent.keycode = 66, KeySym65509, keySymbol65509
numChars = 0,0, 39
keySymbol = 65509


keyevent.keycode = 66, KeySym65509, keySymbol65509

numChars = 0,0, 39

keySymbol = 65509



keyevent.keycode = 38, KeySym1734, keySymbol1734

numChars = 0,0, 39

keySymbol = 1734



keyevent.keycode = 38, KeySym1734, keySymbol1734

numChars = 0,0, 39

keySymbol = 1734



keyevent.keycode = 38, KeySym1734, keySymbol1734

numChars = 0,0, 39

keySymbol = 1734



keyevent.keycode = 38, KeySym1734, keySymbol1734

numChars = 0,0, 39

keySymbol = 1734



keyevent.keycode = 56, KeySym1737, keySymbol1737

numChars = 0,0, 39

keySymbol = 1737



keyevent.keycode = 56, KeySym1737, keySymbol1737

numChars = 0,0, 39

keySymbol = 1737



keyevent.keycode = 56, KeySym1737, keySymbol1737

numChars = 0,0, 39

keySymbol = 1737



keyevent.keycode = 54, KeySym1747, keySymbol1747

numChars = 0,0, 39

keySymbol = 1747



keyevent.keycode = 54, KeySym1747, keySymbol1747

numChars = 0,0, 39

keySymbol = 1747



keyevent.keycode = 40, KeySym1751, keySymbol1751

numChars = 0,0, 39

keySymbol = 1751



keyevent.keycode = 40, KeySym1751, keySymbol1751

numChars = 0,0, 39

keySymbol = 1751



keyevent.keycode = 40, KeySym1751, keySymbol1751

numChars = 0,0, 39

keySymbol = 1751



keyevent.keycode = 66, KeySym65509, keySymbol65509

numChars = 0,0, 39

keySymbol = 65509



keyevent.keycode = 66, KeySym65509, keySymbol65509

numChars = 0,0, 39

keySymbol = 65509



keyevent.keycode = 38, KeySym1766, keySymbol1766

numChars = 0,0, 39

keySymbol = 1766



keyevent.keycode = 38, KeySym1766, keySymbol1766

numChars = 0,0, 39

keySymbol = 1766



keyevent.keycode = 56, KeySym1769, keySymbol1769

numChars = 0,0, 39

keySymbol = 1769



keyevent.keycode = 56, KeySym1769, keySymbol1769

numChars = 0,0, 39

keySymbol = 1769



keyevent.keycode = 54, KeySym1779, keySymbol1779

numChars = 0,0, 39

keySymbol = 1779



keyevent.keycode = 54, KeySym1779, keySymbol1779

numChars = 0,0, 39

keySymbol = 1779



keyevent.keycode = 40, KeySym1783, keySymbol1783

numChars = 0,0, 39

keySymbol = 1783

Re: [osg-users] Help. KeyboardEventHandler and native keyboard layout bug in Linux

[Robert Osfield]

Hi Maxim,

Thanks for the test results.  With the Russian keyboard/locale could
do send us the results of

'ABCD' and then 'abcd'

Robert.

On Mon, Jun 1, 2009 at 3:06 PM, Maxim Gammer  wrote:
> hi,
>
> set OSG_NOTIFY_LEVEL=INFO
> I press "ABCD" (Russian) "ABCD" (USA) 
>
> keyevent.keycode = 38, KeySym1734, keySymbol34001
> numChars = 2,209, 132
> keySymbol = 34001
>
> keyevent.keycode = 38, KeySym1734, keySymbol34001
> numChars = 2,209, 132
> keySymbol = 34001
>
> keyevent.keycode = 56, KeySym1737, keySymbol47312
> numChars = 2,208, 184
> keySymbol = 47312
>
> keyevent.keycode = 56, KeySym1737, keySymbol47312
> numChars = 2,208, 184
> keySymbol = 47312
>
> keyevent.keycode = 54, KeySym1747, keySymbol33233
> numChars = 2,209, 129
> keySymbol = 33233
>
> keyevent.keycode = 54, KeySym1747, keySymbol33233
> numChars = 2,209, 129
> keySymbol = 33233
>
> keyevent.keycode = 40, KeySym1751, keySymbol45776
> numChars = 2,208, 178
> keySymbol = 45776
>
> keyevent.keycode = 40, KeySym1751, keySymbol45776
> numChars = 2,208, 178
> keySymbol = 45776
>
> keyevent.keycode = 37, KeySym65507, keySymbol65507
> numChars = 0,0, 41
> keySymbol = 65507
>
> keyevent.keycode = 50, KeySym65034, keySymbol65034
> numChars = 0,0, 41
> keySymbol = 65034
>
> keyevent.keycode = 50, KeySym65034, keySymbol65034
> numChars = 0,0, 41
> keySymbol = 65034
>
> keyevent.keycode = 37, KeySym65507, keySymbol65507
> numChars = 0,0, 41
> keySymbol = 65507
>
> keyevent.keycode = 38, KeySym97, keySymbol97
> numChars = 1,97, 0
> keySymbol = 97
>
> keyevent.keycode = 38, KeySym97, keySymbol97
> numChars = 1,97, 0
> keySymbol = 97
>
> keyevent.keycode = 56, KeySym98, keySymbol98
> numChars = 1,98, 0
> keySymbol = 98
>
> keyevent.keycode = 56, KeySym98, keySymbol98
> numChars = 1,98, 0
> keySymbol = 98
>
> keyevent.keycode = 54, KeySym99, keySymbol99
> numChars = 1,99, 0
> keySymbol = 99
>
> keyevent.keycode = 54, KeySym99, keySymbol99
> numChars = 1,99, 0
> keySymbol = 99
>
> keyevent.keycode = 54, KeySym99, keySymbol99
> numChars = 1,99, 0
> keySymbol = 99
>
> keyevent.keycode = 40, KeySym100, keySymbol100
> numChars = 1,100, 0
> keySymbol = 100
>
> keyevent.keycode = 40, KeySym100, keySymbol100
> numChars = 1,100, 0
> keySymbol = 100
>
> keyevent.keycode = 76, KeySym65479, keySymbol65479
> numChars = 0,0, 41
> keySymbol = 65479
>
>
> Maxim Gammer
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Help. KeyboardEventHandler and native keyboard layout bug in Linux

[Melchior FRANZ]

Seems to work OK here.

m.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Help. KeyboardEventHandler and native keyboard layout bug in Linux

[Maxim Gammer]

hi,

set OSG_NOTIFY_LEVEL=INFO
I press "ABCD" (Russian) "ABCD" (USA) 

keyevent.keycode = 38, KeySym1734, keySymbol34001
numChars = 2,209, 132
keySymbol = 34001

keyevent.keycode = 38, KeySym1734, keySymbol34001
numChars = 2,209, 132
keySymbol = 34001

keyevent.keycode = 56, KeySym1737, keySymbol47312
numChars = 2,208, 184
keySymbol = 47312

keyevent.keycode = 56, KeySym1737, keySymbol47312
numChars = 2,208, 184
keySymbol = 47312

keyevent.keycode = 54, KeySym1747, keySymbol33233
numChars = 2,209, 129
keySymbol = 33233

keyevent.keycode = 54, KeySym1747, keySymbol33233
numChars = 2,209, 129
keySymbol = 33233

keyevent.keycode = 40, KeySym1751, keySymbol45776
numChars = 2,208, 178
keySymbol = 45776

keyevent.keycode = 40, KeySym1751, keySymbol45776
numChars = 2,208, 178
keySymbol = 45776

keyevent.keycode = 37, KeySym65507, keySymbol65507
numChars = 0,0, 41
keySymbol = 65507

keyevent.keycode = 50, KeySym65034, keySymbol65034
numChars = 0,0, 41
keySymbol = 65034

keyevent.keycode = 50, KeySym65034, keySymbol65034
numChars = 0,0, 41
keySymbol = 65034

keyevent.keycode = 37, KeySym65507, keySymbol65507
numChars = 0,0, 41
keySymbol = 65507

keyevent.keycode = 38, KeySym97, keySymbol97
numChars = 1,97, 0
keySymbol = 97

keyevent.keycode = 38, KeySym97, keySymbol97
numChars = 1,97, 0
keySymbol = 97

keyevent.keycode = 56, KeySym98, keySymbol98
numChars = 1,98, 0
keySymbol = 98

keyevent.keycode = 56, KeySym98, keySymbol98
numChars = 1,98, 0
keySymbol = 98

keyevent.keycode = 54, KeySym99, keySymbol99
numChars = 1,99, 0
keySymbol = 99

keyevent.keycode = 54, KeySym99, keySymbol99
numChars = 1,99, 0
keySymbol = 99

keyevent.keycode = 54, KeySym99, keySymbol99
numChars = 1,99, 0
keySymbol = 99

keyevent.keycode = 40, KeySym100, keySymbol100
numChars = 1,100, 0
keySymbol = 100

keyevent.keycode = 40, KeySym100, keySymbol100
numChars = 1,100, 0
keySymbol = 100

keyevent.keycode = 76, KeySym65479, keySymbol65479
numChars = 0,0, 41
keySymbol = 65479


Maxim Gammer
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] osgGA::GUIEventAdapter::MOVE: doesnt work

[Matthias Asselborn]

ive fied this problem.

the reason was glut 
ive forgotten to declare a passiveMouse Callback 

sorry ... ;-) 

now it works perfect ;-)

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=13261#13261





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

[osg-users] Problems using setResizeNonPowerOfTwoHint(false);

[Tomlinson, Gordon]

Hi 
 
Were having problems with textures that are non power of 2 or power 2 if
we use   m_texture->setResizeNonPowerOfTwoHint(false);
we get no texture
 
The engineer who spotted this says this post
http://www.mail-archive.com/osg-users@lists.openscenegraph.org/msg15206.
html
 
had a fix but looks like it never made it submission or was maybe
rejects , does any one elsehave this issue,  was this fix  ever applied
?
 
Fails in 2.8
Works in 2.3/4
 
 
 
 
 
 
 
 

Gordon
Product Manager 3d
__
Gordon Tomlinson
Email  : gtomlinson @ overwatch.textron.com
__
(C): (+1) 571-265-2612
(W): (+1) 703-437-7651

"Self defence is not a function of learning tricks 
but is a function of how quickly and intensely one 
can arouse one's instinct for survival" 
- Master Tambo Tetsura

 
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] osgGA::GUIEventAdapter::MOVE: doesnt work

[Robert Osfield]

On Mon, Jun 1, 2009 at 2:17 PM, Matthias Asselborn
 wrote:
> Thank you Robert
>
> your example works perfect
> this is exactly what i need
> what osg version did you use?
> did you change only code in the swith case section?

svn/trunk, but it's something that has worked forever.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Help. KeyboardEventHandler and native keyboard layout bug in Linux

[Robert Osfield]

Hi Melchior,

On Mon, Jun 1, 2009 at 2:01 PM, Melchior FRANZ  wrote:
> * Robert Osfield -- Monday 01 June 2009:
>> I've refactored the adaptKey method to use XLookupString in a bit more
>> thorough way to than it did before, it ensures that osgkeyboard works
>> fine on my Linux box with UK keyboard.  Could you try this?
>
> Umm ... did you try osgkeyboard this time?

Yes.

> This patch swallows Backspace.

I missed this one.  Delete was also not working.  Could you try the
attached GraphicsWindowX11.cpp.

> Frankly, I find all these recent keyboard hacks rather worrying. I'd
> really like Maxim to provide more info about the problem first (as you
> suggested in your last post). Better let the keyboard as it was for now.
>
> This could be a broken X server on his side (devel version or something),
> or a broken setup or whatever. I can't believe that he's the only one
> with a russian keyboard. Looks like everyone elses works just fine.

It's extremely frustrating for me to have a regression slip through.
I have requested more info from Maxim about exactly what is happening
at his end.  Feedback from others with Russian keyboards would also be
useful.

Robert.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] osgGA::GUIEventAdapter::MOVE: doesnt work

[Matthias Asselborn]

Thank you Robert

your example works perfect 
this is exactly what i need 
what osg version did you use?
did you change only code in the swith case section?

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=13258#13258





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Help. KeyboardEventHandler and native keyboard layout bug in Linux

[Melchior FRANZ]

* Robert Osfield -- Monday 01 June 2009:
> I've refactored the adaptKey method to use XLookupString in a bit more
> thorough way to than it did before, it ensures that osgkeyboard works
> fine on my Linux box with UK keyboard.  Could you try this?

Umm ... did you try osgkeyboard this time? This patch swallows Backspace.
Frankly, I find all these recent keyboard hacks rather worrying. I'd
really like Maxim to provide more info about the problem first (as you
suggested in your last post). Better let the keyboard as it was for now.

This could be a broken X server on his side (devel version or something),
or a broken setup or whatever. I can't believe that he's the only one
with a russian keyboard. Looks like everyone elses works just fine.

m.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] osgGA::GUIEventAdapter::MOVE: doesnt work

[Robert Osfield]

Hi Mathias,

I have just modified the osgpick example to check for MOVE events and
it works perfectly.

switch(ea.getEventType())
{
case(osgGA::GUIEventAdapter::MOVE):
{
osgViewer::View* view = dynamic_cast(&aa);
if (view) pick(view,ea);
return false;
}

I don't know what you've done wrong, but perhaps you can look at the
attached osgpick.cpp for reference.

Robert.


On Mon, Jun 1, 2009 at 1:30 PM, Matthias Asselborn
 wrote:
> iam holding the mouse button not down.
>
> i want a pick each time i move my mouse!
> i thought its implemented with : MOVE ...
> but its not working
>
> ...
>
> Thank you!
>
> Cheers,
> Matthias
>
> --
> Read this topic online here:
> http://forum.openscenegraph.org/viewtopic.php?p=13254#13254
>
>
>
>
>
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
/* OpenSceneGraph example, osgpick.
*
*  Permission is hereby granted, free of charge, to any person obtaining a copy
*  of this software and associated documentation files (the "Software"), to deal
*  in the Software without restriction, including without limitation the rights
*  to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
*  copies of the Software, and to permit persons to whom the Software is
*  furnished to do so, subject to the following conditions:
*
*  THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
*  IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
*  FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
*  AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
*  LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
*  OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
*  THE SOFTWARE.
*/

/* osgpick sample
* demonstrate use of osgUtil/PickVisitor for picking in a HUD or
* in a 3d scene,
*/

#include 
#include 
#include 
#include 

#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 

#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 
#include 

#include 

#include 

// class to handle events with a pick
class PickHandler : public osgGA::GUIEventHandler {
public: 

PickHandler(osgText::Text* updateText):
_updateText(updateText) {}

~PickHandler() {}

bool handle(const osgGA::GUIEventAdapter& ea,osgGA::GUIActionAdapter& aa);

virtual void pick(osgViewer::View* view, const osgGA::GUIEventAdapter& ea);

void setLabel(const std::string& name)
{
if (_updateText.get()) _updateText->setText(name);
}

protected:

osg::ref_ptr  _updateText;
};

bool PickHandler::handle(const osgGA::GUIEventAdapter& ea,osgGA::GUIActionAdapter& aa)
{
switch(ea.getEventType())
{
case(osgGA::GUIEventAdapter::MOVE):
{
osgViewer::View* view = dynamic_cast(&aa);
if (view) pick(view,ea);
return false;
}
case(osgGA::GUIEventAdapter::PUSH):
{
osgViewer::View* view = dynamic_cast(&aa);
if (view) pick(view,ea);
return false;
}
case(osgGA::GUIEventAdapter::KEYDOWN):
{
if (ea.getKey()=='c')
{
osgViewer::View* view = dynamic_cast(&aa);
osg::ref_ptr event = new osgGA::GUIEventAdapter(ea);
event->setX((ea.getXmin()+ea.getXmax())*0.5);
event->setY((ea.getYmin()+ea.getYmax())*0.5);
if (view) pick(view,*event);
}
return false;
}
default:
return false;
}
}

void PickHandler::pick(osgViewer::View* view, const osgGA::GUIEventAdapter& ea)
{
osgUtil::LineSegmentIntersector::Intersections intersections;

std::string gdlist="";
float x = ea.getX();
float y = ea.getY();
#if 0
osg::ref_ptr< osgUtil::LineSegmentIntersector > picker = new osgUtil::LineSegmentIntersector(osgUtil::Intersector::WINDOW, x, y);
osgUtil::IntersectionVisitor iv(picker.get());
view->getCamera()->accept(iv);
if (picker->containsIntersections())
{
intersections = picker->getIntersections();
#else
if (view->computeIntersections(x,y,intersections))
{
#endif
for(osgUtil::LineSegmentIntersector::Intersections::iterator hitr = intersections.begin();
hitr != intersections.end();
++hitr)
{
std::ostringstream os;
if (!hitr->nodePath.empty() && !(hitr->nodePath.back()->getName().empty()))
{
// the geodes are identified by name.
os<<"Object \""getName()<<"\""

Re: [osg-users] Help. KeyboardEventHandler and native keyboard layout bug in Linux

[Robert Osfield]

Hi Maximum,

On Mon, Jun 1, 2009 at 1:06 PM, Maxim Gammer  wrote:
> modified GraphicsWindowX11.cpp not work fine (((

Could you post the command line output that it generates, and this
might give us a bit more a clue why your system things go wrong, but
on the majority of other systems things work fine.

Could you also provide some information about your keyboard type and
how you've gone about setting the locale?

Robert.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] osgGA::GUIEventAdapter::MOVE: doesnt work

[Matthias Asselborn]

iam holding the mouse button not down.

i want a pick each time i move my mouse! 
i thought its implemented with : MOVE ...
but its not working 

... 

Thank you!

Cheers,
Matthias

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=13254#13254





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Help. KeyboardEventHandler and native keyboard layout bug in Linux

[Maxim Gammer]

Hi,

modified GraphicsWindowX11.cpp not work fine (((


Maxim Gammer


2009/6/1 Robert Osfield :
> Hi Melchior,
>
> I've refactored the adaptKey method to use XLookupString in a bit more
> thorough way to than it did before, it ensures that osgkeyboard works
> fine on my Linux box with UK keyboard.  Could you try this?
>
> Cheers,
> Robert.
>
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
>



-- 
Maxim Gammer
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] osg::ref_ptr<> used anymore

[Ismail Pazarbasi]

2009/6/1 James Killian :
>>  The real question is -- does boost even offer a smart pointer type that
>> replicates
>> ref_ptr, or is all this a pointless exercise?
>
> I've stepped through ref_ptr code before and it does seem similar to
> intrusive and perhaps shared as well.  I have also discovered a few matrix
> classes that are public one of which is optimized SSE and SSE2, where some
> of the benchmark code pointed out a standard to work with them among several
> offered (including Microsoft's).
>
> The most attractive thing about standards like std::, boost, and tr1, is
> that they are tested extensively by a wider c++ community and so they must
> be pretty darn robust and more versatile, but more important if you are like
> me and code for more platforms other than osg, you'll find it extremely
> useful to be able to transfer knowledge of one standard and apply it to
> multiple projects with completely different environments.
>
>
> James Killian
> - Original Message - From: "Chris 'Xenon' Hanson"
> 
> To: "OpenSceneGraph Users" 
> Sent: Sunday, May 31, 2009 8:21 PM
> Subject: Re: [osg-users] osg::ref_ptr<> used anymore
>
>
>> Judd Tracy wrote:
>>>
>>> Boost only needs to be installed if you use certain features.  Shared
>>> pointers is not one of those features in which it needs to be
>>> installed.
>>
>>  I like boost myself, and have used parts of it in different projects.
>> But, I want to
>> clarify the sense of "installed" here.
>>
>>  I'd differentiate the multiple meanings of "installed" into
>> headers-installed and
>> libraries-installed. To use any part of boost in your code, you (the
>> person compiling the
>> boost-using project) must have the boost development kit with headers
>> installed. This is
>> one component that OSG doesn't currently require. It's pretty version-safe
>> -- generally if
>> you require boost x.y.z, any version > than that should be fine.
>>
>>  Judd is right in that most of boost does its magic at compile-time and
>> doesn't need
>> binary libraries at link-time.
>>
>>  However, it seems it is still possible to get in trouble when you mix
>> binaries compiled
>> by different people who used different versions of boost -- whether they
>> were using
>> compile-time or link-time portions of boost.
>>
>>  Because OSG incorporates other third-party libraries (such as Collada)
>> that incorporate
>> boost and are difficult for individual OSG developers or the project
>> maintainers to
>> recompile every time something changes, we've run afoul of this problem
>> and are gun-shy.
>>
>>  The real question is -- does boost even offer a smart pointer type that
>> replicates
>> ref_ptr, or is all this a pointless exercise?
>>
>> --
>> Chris 'Xenon' Hanson, omo sanza lettere                  Xenon
>> AlphaPixel.com
>> PixelSense Landsat processing now available!
>> http://www.alphapixel.com/demos/
>> "There is no Truth. There is only Perception. To Perceive is to Exist." -
>> Xen
>> ___
>> osg-users mailing list
>> osg-users@lists.openscenegraph.org
>> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>>
>
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>

Paul,

The reason why people think boost is big probably because they
misinterpret "library" word. Some certain type of developers I saw (I
worked with those before) wants to understand everything about piece
of code written by others, which sometimes may not be possible, if one
doesn't:
* know language that advanced
* know the purpose exactly
* have the experience required to implement such a thing
I can't name project exactly, but it was a set of template classes
trying to address a common problem nearly entire team was having
problem with. Current implementation was to use bunch of macros, and
#ifdefs. The reason behind this language level approach was to remove
as many of those preprocessor garbage away from the actual source code
- because we (2 devs) believed it's difficult to read and debug the
code (you can't set breakpoint to next few lines, because you don't
know whether that macro was defined before). It turned out that some
devs believe our template solution could defect readability of source
code. I didn't push much but during an informal conversation kindly
asked with coffee in our hands in a cold winter's day; did you walk
through std::map's source code before? It's a well known, well
documented, standard and perfectly readable code! He said "no, because
I don't think STL code is readable either". He probably can't read
Windows SDK source code either, but _uses_ it. Everybody has different
skills at different levels and may have emphasized different aspects
of software design/implementation. But libraries aren't meant to be
_read_, they are to _used_.

Chris,

the discussions wasn't about comparing 

Re: [osg-users] Website not reachable from france and austria

[Cedric Pinson]

Hi Jose,
libvirt is the futur, if i remember you need to have some special
instruction on the cpu to use it with kvm. Most people around me are
switching from vserver to libvirt, i have not made the switch yet, so if
you need vserver i can help you on it, and provide you one or more
quickly. But it should be considered as temporary solution because
libvirt is the best way. IMO

Cheers,
Cedric

On Mon, 2009-06-01 at 12:35 +0200, Jose Luis Hidalgo wrote:
> Hi All,
> 
>We've had a problem with the host of our OSG virtual machine, looks
> like we are having problems with the vmware that we are currently
> using. I'm considering the possibility to move to another
> virtualization technology , like libvirt, does any of you have insight
> into wich one is better?
> 
> 
> BTW, the host is up again.
> 
> Cheers,
>Jose-Luis.
> 
> 
> 
> On Mon, Jun 1, 2009 at 10:53 AM, Robert Osfield
>  wrote:
> > Hi Johannes,
> >
> > Looks like the main openscenegraph.org server is down.  I've been
> > offline most of the weekend so haven't spotted this.
> >
> > The blog and forum and mailing list are all hosted on different
> > servers to the main website + subversion so won't be affected by
> > problems with the main server.
> >
> > I'll contact Jose Luis to see what is up.
> >
> > Robert.
> >
> > On Sat, May 30, 2009 at 8:39 PM, Johannes Schüth  wrote:
> >> Hi,
> >>
> >> i can access:
> >>
> >> blog.openscenegraph.org
> >> forum.openscenegraph.org
> >>
> >> but not www.openscenegraph.org / openscenegraph.org
> >>
> >> Seems to be a dns problem?
> >>
> >> ping www.openscenegraph.org
> >> PING lemonvm-osg.ai2.upv.es (158.42.9.50) 56(84) bytes of data.
> >>
> >> Thank you!
> >>
> >> Cheers,
> >> Johannes
> >>
> >> --
> >> Read this topic online here:
> >> http://forum.openscenegraph.org/viewtopic.php?p=13213#13213
> >>
> >>
> >>
> >>
> >>
> >> ___
> >> osg-users mailing list
> >> osg-users@lists.openscenegraph.org
> >> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
> >>
> > ___
> > osg-users mailing list
> > osg-users@lists.openscenegraph.org
> > http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
> >
> 
> 
> 
-- 
+33 (0) 6 63 20 03 56  Cedric Pinson mailto:cedric.pin...@plopbyte.net
http://www.plopbyte.net



signature.asc
Description: This is a digitally signed message part
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Website not reachable from france and austria

[Jose Luis Hidalgo]

Hi All,

   We've had a problem with the host of our OSG virtual machine, looks
like we are having problems with the vmware that we are currently
using. I'm considering the possibility to move to another
virtualization technology , like libvirt, does any of you have insight
into wich one is better?


BTW, the host is up again.

Cheers,
   Jose-Luis.



On Mon, Jun 1, 2009 at 10:53 AM, Robert Osfield
 wrote:
> Hi Johannes,
>
> Looks like the main openscenegraph.org server is down.  I've been
> offline most of the weekend so haven't spotted this.
>
> The blog and forum and mailing list are all hosted on different
> servers to the main website + subversion so won't be affected by
> problems with the main server.
>
> I'll contact Jose Luis to see what is up.
>
> Robert.
>
> On Sat, May 30, 2009 at 8:39 PM, Johannes Schüth  wrote:
>> Hi,
>>
>> i can access:
>>
>> blog.openscenegraph.org
>> forum.openscenegraph.org
>>
>> but not www.openscenegraph.org / openscenegraph.org
>>
>> Seems to be a dns problem?
>>
>> ping www.openscenegraph.org
>> PING lemonvm-osg.ai2.upv.es (158.42.9.50) 56(84) bytes of data.
>>
>> Thank you!
>>
>> Cheers,
>> Johannes
>>
>> --
>> Read this topic online here:
>> http://forum.openscenegraph.org/viewtopic.php?p=13213#13213
>>
>>
>>
>>
>>
>> ___
>> osg-users mailing list
>> osg-users@lists.openscenegraph.org
>> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>>
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>



-- 
  Jose L. Hidalgo Valiño (PpluX)
   http://www.pplux.com 
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Help. KeyboardEventHandler and native keyboard layout bug in Linux

[Melchior FRANZ]

* Robert Osfield -- Monday 01 June 2009:
> Clearly it's not [now] badly broken so we'll have to find another route.
> I do some investigation at my end.

Here's how to deal with it (once SVN is up again :-):

  $ svn diff -r10268:10269|patch -p0 -R

Now the question is: what's up with russian keyboards? Are we really to
assume that X can't handle them, unlike any other layout? We were using
XLookupString(), and that should do the right thing for any keyboard, no?
Could Maxim's problem stem from a local misconfiguration at his machine?
Any other Russian users out there who could shed a light on the issue?

Maybe GraphicsWindowX11cpp should only change it's former (right)
behaviour if a key returns 0, as it was in Maxim's case? (0 is a
valid value, though. You get it with Ctrl-Space.) 

m
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Help. KeyboardEventHandler and native keyboard layout bug in Linux

[Robert Osfield]

Hi Melchior,

Argg... one step forward twenty back..  sadly I didn't test with
osgkeyboad when I made the fix.  Clearly it's not badly broken so
we'll have to find another route.  I do some investigation at my end.

Robert.

On Mon, Jun 1, 2009 at 9:18 AM, Melchior FRANZ  wrote:
> * Robert Osfield -- Monday 25 May 2009:
>> Good to hear that it's now working.
>
> Sorry, but it's not! This totally breaks non-russian keyboards. Did you
> try osgkeyboard lately? Type an upper-case letter. You'll get lower-case
> instead.
>
> The code that you threw out was meant to turn lowercase into uppercase when
> shift was pressed, and ctrl-codes to the control range (ctr-a -> 0x1). Now
> we always get 'a', no matter which modifiers are pressed. (The modifiers
> themselves are still reported correctly, of course.)
>
> I don't say that the new behavior is wrong, but it'll break about *any*
> keyboard using program out there. If this is to stay, then all of them have
> to be adapted and do the conversion themselves.
>
> Here's a comparison of what we got before and what we get now. The numbers
> are getModKeyMask()-getKey().
>
> Typing    before r10269                     with r10269
> ---
> a         -0061 'a' shift:   ctrl:      -0061 'a' shift:   ctrl:
> Shift-a   0001-0041 'A' shift: L ctrl:      0001-0061 'a' shift: L ctrl:
> Ctrl-a    0004-0001     shift:   ctrl: L    0004-0061 'a' shift:   ctrl: L
>
>
> I've got the attached patch applied to osgkeyboard.cpp ever since I worked on
> GraphicsWindowX11.cpp. This outputs some more useful information than it does
> normally.
>
> m.
>
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
>
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Website not reachable from france and austria

[Robert Osfield]

Hi Johannes,

Looks like the main openscenegraph.org server is down.  I've been
offline most of the weekend so haven't spotted this.

The blog and forum and mailing list are all hosted on different
servers to the main website + subversion so won't be affected by
problems with the main server.

I'll contact Jose Luis to see what is up.

Robert.

On Sat, May 30, 2009 at 8:39 PM, Johannes Schüth  wrote:
> Hi,
>
> i can access:
>
> blog.openscenegraph.org
> forum.openscenegraph.org
>
> but not www.openscenegraph.org / openscenegraph.org
>
> Seems to be a dns problem?
>
> ping www.openscenegraph.org
> PING lemonvm-osg.ai2.upv.es (158.42.9.50) 56(84) bytes of data.
>
> Thank you!
>
> Cheers,
> Johannes
>
> --
> Read this topic online here:
> http://forum.openscenegraph.org/viewtopic.php?p=13213#13213
>
>
>
>
>
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] smooth angle on normal calculation

[Robert Osfield]

Hi Matthias,

What do you mean "recalculate the normals to 30 degrees"?  This really
doesn't mean anything without more specific information about what you
are after.

The SmoothingVisitor is a straight forward implementation that smooth
all normals, there are no additional controls/things that you can
adjust to get different results.

Robert.

On Sat, May 30, 2009 at 4:23 PM, Matthias Asselborn
 wrote:
> Hi,
>
> i need a smooth with recalculate normals of 30 degrees
> the left side of picture shows a smoothed version
> with smoot visitor. The right side without it.
> can i recalculate the normals to 30 degrees with smooth visitor?
>
> Thank you!
>
> Cheers,
> Matthias
>
> --
> Read this topic online here:
> http://forum.openscenegraph.org/viewtopic.php?p=13210#13210
>
>
>
>
> ___
> osg-users mailing list
> osg-users@lists.openscenegraph.org
> http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
>
>
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Osg steteo problems!! Help!!!

[Robert Osfield]

HI Helong,

2009/5/30 神和龙 :
>1.  When I use this function to configure the fusion distance,
>
> setFusionDistance(osgUtil::SceneView::USE_FUSION_DISTANCE_VALUE ,
> fusionDistance)
>
> It seems none effect. As it is calculated automatically by osg and equals to
> the distance between eye and the center of the scene. How can control it?


The fusion distance is used during for automatic compute of the
interocular distance (distance between left and right eyes) in world
space, but it's only used with certain camera manipulators - the
trackball and terrain manipulators.

What end effect are you looking for?


>2.   How to realize the stereo effect of the prerender texture?
>
> I use a camera to render the normal scene and another prerender
> camera to render the reflect texture of the scene. The normal scene can get
> stereo effects. But the texture in prerender camera couldn't have stereo
> effects.
>
>How can the prerender camera are controlled by the stereo parameters.

The best way to achieve this is to here two render to texture
subgraphs, one for each eye, and have the cull traversal choose
between these based on a cull traversal mask.  Have a look at the
osgstrereoimage example for an example of left/right eye subgraphs in
action.

Robert.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Help. KeyboardEventHandler and native keyboard layout bug in Linux

[Melchior FRANZ]

* Melchior FRANZ -- Monday 01 June 2009:
> I don't say that the new behavior is wrong, but [...]

Oh, wait. That's exactly what I'm saying. It's dead wrong. 'a' was just
a harmless example. Applications could work around that. But check this:


  Typingbefore r10269  with r10269
  ---
  - -002d  '-'  shift: -002d  '-'  shift:
  _ (shift--)   0001-005f  '_'  shift: L   0001-002d  '-'  shift: L
  = -003d  '='  shift: -003d  '='  shift:
  + (shift-=)   0001-002b  '+'  shift: L   0001-003d  '='  shift: L
  \ -005c  '\'  shift: -005c  '\'  shift:
  | (shift-\)   0001-007c  '|'  shift: L   0001-005c  '\'  shift: L
  ` -0060  '`'  shift: -0022  '"'  shift:
  ~ (shift-`)   0001-007e  '~'  shift: L   0001-0022  '"'  shift: L


So Shift-+ is now turned into '=', but applications can't restore '+'
from 0001-003d without knowing the keyboard layout. So they'd have
to use X functions directly, and that breaks cross-platformness.

m.
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Help. KeyboardEventHandler and native keyboard layout bug in Linux

[Melchior FRANZ]

* Robert Osfield -- Monday 25 May 2009:
> Good to hear that it's now working.

Sorry, but it's not! This totally breaks non-russian keyboards. Did you
try osgkeyboard lately? Type an upper-case letter. You'll get lower-case
instead.

The code that you threw out was meant to turn lowercase into uppercase when
shift was pressed, and ctrl-codes to the control range (ctr-a -> 0x1). Now
we always get 'a', no matter which modifiers are pressed. (The modifiers
themselves are still reported correctly, of course.)

I don't say that the new behavior is wrong, but it'll break about *any*
keyboard using program out there. If this is to stay, then all of them have
to be adapted and do the conversion themselves.

Here's a comparison of what we got before and what we get now. The numbers
are getModKeyMask()-getKey().

Typingbefore r10269 with r10269
---
a -0061 'a' shift:   ctrl:  -0061 'a' shift:   ctrl:
Shift-a   0001-0041 'A' shift: L ctrl:  0001-0061 'a' shift: L ctrl:
Ctrl-a0004-0001 shift:   ctrl: L0004-0061 'a' shift:   ctrl: L


I've got the attached patch applied to osgkeyboard.cpp ever since I worked on
GraphicsWindowX11.cpp. This outputs some more useful information than it does
normally.

m.
Index: osgkeyboard.cpp
===
--- osgkeyboard.cpp	(revision 10292)
+++ osgkeyboard.cpp	(working copy)
@@ -16,6 +16,8 @@
 *  THE SOFTWARE.
 */
 
+#include 
+
 #include 
 #include 
 #include 
@@ -360,6 +362,8 @@
 
 
 
+#include 
+#include 
 class KeyboardEventHandler : public osgGA::GUIEventHandler
 {
 public:
@@ -374,13 +378,13 @@
 
 //osg::notify(osg::NOTICE)<<"Mouse "<___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Website not reachable from france and austria

[daniele argiolas]

also from Italy

--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=13235#13235





___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org

Re: [osg-users] Transparency and hdr texture

[Ragnar Hammarqvist]

The OpenExr implementation in Osg only supports the half-float format. It can 
load Textures saved in 32bits per pixel but the loader converts them into half 
float. But the loader however supports an Alfa channel.

The OpenExr plug-in can be extended to support 32-bits textures but that would 
require some head scratching and someone diving into the OpenEXR interface 
documentation. http://www.openexr.com/documentation.html

Regards Ragnar

-Ursprungligt meddelande-
Från: osg-users-boun...@lists.openscenegraph.org 
[mailto:osg-users-boun...@lists.openscenegraph.org] För Jason Daly
Skickat: den 29 maj 2009 17:04
Till: OpenSceneGraph Users
Ämne: Re: [osg-users] Transparency and hdr texture

josselin.pe...@lcpc.fr wrote:
> Hi,
>
> Does anyone know an image format storing high dynamic range values (32 
> bits per pixel) and transparency ?
>   

I believe OSG supports OpenEXR, which was designed by Industrial Light 
and Magic for this purpose.  I think it supports both half-float and 
float formats, and it's probably the highest-quality format for HDR 
pictures.  There is also the HDR format, but I think it only does RGBE, 
not float.

--"J"
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org
___
osg-users mailing list
osg-users@lists.openscenegraph.org
http://lists.openscenegraph.org/listinfo.cgi/osg-users-openscenegraph.org