Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
OpenWalnut Core OpenWalnut Core
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 82
    • Issues 82
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • OpenWalnut
  • OpenWalnut CoreOpenWalnut Core
  • Issues
  • #50

Closed
Open
Created May 08, 2017 by Mathias Goldau@mathOwner

-RM-373-MR-[NavigationSlices] The slice positions of the NavigationSlices should be available to other modules as well

As many slice-based modules will typicall use our colormapping meachnism to display some context with navslices we should provide an output connector for the slices positions of the navslice module. Ideally the modules should not spy each other, nor they should forward properties to other modules. Hence, they should make only the relevant data available. I guess the best way to realize this is a subscription to the property updateConditions. As module connector I propose to encapsulate it as WPosition (for x, y and z position of the axis aligned navigation slices).

(from redmine: created on 2014-07-22, closed on 2014-07-22)

Assignee
Assign to
OpenWalnut 1.4
Milestone
OpenWalnut 1.4
Assign milestone
Time tracking