omegalib 3.5 released

-
o3.5

Major Changes

  • Reorganized source: all c++ and python examples are now under /examples.
  • (3.5.1) omicron and omegalib use double precision math by default.

omega

  • Improvements to python API
  • Camera.focusOn
  • clip plane control
  • (3.5.1) fixes to SceneNode? bounding box
  • NodeComponent? API slightly changed to support more functionality for objects attached to scene nodes.
  • (3.5.1) ImageUtils::loadImageFromStream()
  • (3.5.1) Keyboard service generates button left/right/up/down events when keyboard arrows are used.

    omegaOsg

    • fixed bounding box generation
    • fixes to clipping
    • (3.5.1) Added auto near / far Z computation toggle (:setautonearfar [on|off])
    • (3.5.1) Added support for PagedLOD and DatabasePager?
    • (3.5.1) FBX support can be optionally disabled

    omegaVtk

    • re-added support for vtk python scripting
    • added support for vtk lights.
    • added support for depth peeling

      cyclops

        • Context menus can be attached to entities using a simpler API that does not require custom scripting.
        • Added support for custom model loaders
        • GPU Program assets are now fully configurable through python (using the ProgramAsset class). Programs can be reloaded at runtime using a simple command (SceneManager.updateProgram) allowing users to experiment with different shaders.

          orun

            • configurable startup script and application start function. The startup script can be used as a 'boot' script to modify applications depending on the system they are running on. The application start function (typically defined in the init script) is launched every time a new application starts and can be used to inject cutom functions (like system menus) into the application.

              omegaToolkit

                • (3.5.1) added Container:isEventInside, other improvements and fixes to ui Container class
                • (3.5.1) improved AppDrawer
                • (3.5.1) custom user data can be attached to Widget
                • (3.5.1) Button icons

                Comments

                Post a Comment

                Popular posts from this blog

                Flickering 2D transform elements in Chrome: a simple fix

                -
                This quick post is to point out a fix to an issue I had to deal with a few weeks ago and was caused by a Chrome update. Components with absolute positioning and a 2D CSS transform started flickering when placed inside a scrollable component. A brief search online revealed several people with similar problems, but the suggested fixes were all very different. I tested several of them (including obvious changes to the z order) before finding the one that actually did the trick. What eventually worked for me was adding an empty 3D transform to the same elements with 2D transforms: transform:translate3d(0,0,0); I guess the reason why this works is that it forces elements to be drawn via a different rendering / compositing path than standard 2D elements.
                Read more

                glVertexAttribPointer and double precision buffers

                -
                Image
                This post will hopefully help people avoid a mistake that cost me several hours of debugging. In one of my projects I have been working with OpenGL 4 double precision vertex buffers. As the buffer data was passed to the shader as a generic attribute, I have been using  glVertexAttribPointer  to specify the attribute location in the data stream. This worked fine with floating point data. When I needed to switch to double precision, I checked the glVertexAttribPointer specification: this function accepts GL_DOUBLE as an input type: therefore, I assumed that change was all I needed to pass double precision data to my shader. I noticed two other version of the attrib pointer function existed ( glVertexAttribIPointer and  glVertexAttribLPointer ) but I thought they were just legacy functions or alternatives to using glVertexAttribPointer with GL_DOUBLE or GL_INT type specifiers. Things did not work as I expected. trying to pass double precision data to the shader cau...
                Read more

                Paths to Power: How Every Member Got to Congress

                -
                Image
                An interesting visualization from the New York Times, showing the education and career path of each member of the 116th congress. It outlines how a large number of representatives go through similar milestones, which are divided in three categories (education, career, government).  I was surprised to see that party affiliation does not appear to make a big difference in a representative's career path. With the exception of a few steps like non-profit work, milestones are distributed equally between democrats and republicans. The horizontal axis is not meaningful: I wonder if this would be easier to read as a simple parallel coordinates visualization. The large number of paths also makes it difficult to unveil relations between milestones: did more representatives with career in private law attend public or private college? It would be cool to be able to select a single milestone and see all paths going through it (the visualization allows to hover and view a single path at a ti...
                Read more