Hi, this is a bug indeed. I filed a bug in our bug tracker: http://bugs.mitk.org/show_bug.cgi?id=17572.
Thanks for reporting. Stefan ________________________________________ Von: Martin Klemm [martin.kl...@hs-offenburg.de] Gesendet: Donnerstag, 20. März 2014 16:43 An: Kislinskiy, Stefan; mitk-users@lists.sourceforge.net Betreff: Re: AW: AW: [mitk-users] Expanding Bounding Boxes Hi, thank you. It does what it is supposed to do plus something else that looks like a bug (see image: http://imgur.com/j8AqHSn ). I am rendering a pointer (yellow part) and a blue line. This line is stippled. The problem is that now with the below modifications it shows the frame of the render window also stippled. I also removed the modifications and tried the manual way in the GUI. The frame is just stippled when the crosshair is hidden. This is the code I use in ApplyAllProperties of my line mapper: bool isStippled = false; int stipplePattern; node->GetBoolProperty("stippled", isStippled); if ( isStippled ) { stipplePattern = 0xff00; } else { stipplePattern = 0xffff; } _actor->GetProperty()->SetLineStipplePattern(stipplePattern); Best regards, Martin On 19.03.2014 14:12, Kislinskiy, Stefan wrote: > In all render windows you have an overlay menu in the top right where you can > globally disable the crosshair. If you want to do it programmatically, see > mitk::ILinkedRenderWindowPart::EnableSlicingPlanes(). In a plugin (view), the > code could look like the following: > > mitk::ILinkedRenderWindowPart* linkedRenderWindowPart = > dynamic_cast<mitk::ILinkedRenderWindowPart*>(this->GetRenderWindowPart()); > if (linkedRenderWindowPart != NULL) > linkedRenderWindowPart->EnableSlicingPlanes(false); > > Best, > Stefan > > -----Ursprüngliche Nachricht----- > Von: Martin Klemm [mailto:martin.kl...@hs-offenburg.de] > Gesendet: Mittwoch, 19. März 2014 14:05 > An: Kislinskiy, Stefan; mitk-users@lists.sourceforge.net > Betreff: Re: AW: [mitk-users] Expanding Bounding Boxes > > Sorry. What I meant was to hide the widget planes of a plugin. So the three > rectangles inside the 3D render window that define the 2D slices in the other > three windows. > > Best regards, > > Martin > > On 19.03.2014 10:47, Kislinskiy, Stefan wrote: >> Hi, >> >> what do you mean by "hiding the bounding box"? If you want to hide all >> objects inside your bounding box you have to manually hide each of these >> objects via mitk::DataNode::SetVisibility() or by setting their "visible" >> property to false. >> >> Best, >> Stefan >> ________________________________________ >> Von: Martin Klemm [martin.kl...@hs-offenburg.de] >> Gesendet: Mittwoch, 19. März 2014 09:11 >> An: Kislinskiy, Stefan; mitk-users@lists.sourceforge.net >> Betreff: Re: [mitk-users] Expanding Bounding Boxes >> >> Hi, >> >> thank you very much. That solved this problem. Is there also a way to >> hide the bounding box? >> >> Best Regards, >> >> Martin >> >> On 18.03.2014 19:10, Kislinskiy, Stefan wrote: >>> Hi, >>> >>> you can retrieve Geometry3D instances from your TimeGeometry instances, >>> e.g., by calling GetGeometryForTimestep(). >>> >>> Best, >>> Stefan >>> ________________________________________ >>> Von: Martin Klemm [martin.kl...@hs-offenburg.de] >>> Gesendet: Dienstag, 18. März 2014 15:37 >>> An: mitk-users@lists.sourceforge.net >>> Betreff: [mitk-users] Expanding Bounding Boxes >>> >>> Hello, >>> >>> is there a way to set minimum values for the bounding box? What I >>> want to do is the following: >>> >>> mitk::DataStorage::Pointer ds = _objContainer->GetDataStorage(); >>> >>> // get all nodes that have not set "includeInBoundingBox" to false >>> and compute bounding box >>> if (ds.IsNull()) >>> return; >>> mitk::NodePredicateNot::Pointer pred = mitk::NodePredicateNot::New( >>> mitk::NodePredicateProperty::New("includeInBoundingBox", >>> mitk::BoolProperty::New(false))); >>> mitk::DataStorage::SetOfObjects::ConstPointer rs = ds->GetSubset(pred); >>> mitk::TimeGeometry::Pointer bounds = >>> ds->ComputeBoundingGeometry3D(rs, "visible"); >>> >>> if (bounds.IsNull()) >>> return; >>> >>> bounds->SetExtentInMM(0, 100); >>> bounds->SetExtentInMM(1, 100); >>> bounds->SetExtentInMM(2, 100); >>> >>> The problem is that the last call (SetExtentInMM) does not exist for >>> TimeGeometry, however, it exists for Geometry3D. Does anyone knows a >>> way to solve this? >>> >>> Thank you very much. >>> >>> Best regards >>> >>> ------------------------------------------------------------------------------ Learn Graph Databases - Download FREE O'Reilly Book "Graph Databases" is the definitive new guide to graph databases and their applications. Written by three acclaimed leaders in the field, this first edition is now available. Download your free book today! http://p.sf.net/sfu/13534_NeoTech _______________________________________________ mitk-users mailing list mitk-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mitk-users
