On Sat, Sep 13, 2014 at 3:20 PM, Vlad Bogolin <vladbogo...@gmail.com> wrote:
> At the moment there already are two images: a QImage used for the > framebuffer image and a QPixmap for display manager wireframes. The > disappearing problem is related to the fact that after the raytracing is > complete, the whole scene is redrawn so in order to show it, I set the > QImage as the background and then all the drawing is done over the window > (for the underlay). Makes sense. > In order to have an underlay drawing during raytracing, > I don't know exactly which is the best way to combine the images, because we > need a fast way to extract objects from one image and insert them into the > other. One idea would be to store some sort of objects, not a whole image so > that they could be combined more easily. What do you think? My (naive) thought was to have the display manager image with the wireframe and/or triangles rendered in it use an image alpha channel to be transparent everywhere there wasn't actual geometry or faceplate drawing taking place, and then composite it together with the framebuffer (so, during raytracing, the update will have one extra step when in underlay mode - in overlay mode, of course, there's no need to do anything about showing the dm wireframe at all): http://qt-project.org/doc/qt-4.8/demos-composition.html Again, that's just a notion. For interlay mode, we would need to have a routine that draws the vlists in such a way that it "lifts the pen" anytime the depth goes below the plane representing the framebuffer in the view... I'm not sure how the X drawing handles that currently. Interlay is a bit dubious as a feature, so I'd definitely prioritize working on the Qt window in place of the Tk window over supporting interlay. There has been discussion in the past of simply deprecating "interlay" as a feature completely - perhaps it is time to have that discussion again. Cheers, CY ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ BRL-CAD Developer mailing list brlcad-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/brlcad-devel
