Skip to content
GitLab
    • Explore Projects Groups Topics Snippets
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • railVIVID1 railVIVID1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Graph
    • Compare revisions
  • Issues 58
    • Issues 58
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Tools
  • railVIVID1railVIVID1
  • Issues
  • #42
Something went wrong while setting issue due date.
Closed
Open
Issue created 10 years ago by Administrator@rootOwner
  • New related issue

  • New related issue

Timetable period heading in graphic timetable viewer (de: Fahrplanperiode als Überschrift im Bildfahrplan)

Open

Timetable period heading in graphic timetable viewer (de: Fahrplanperiode als Überschrift im Bildfahrplan)

In some cases additionally to the train heading (see #38 (closed)) a head line showing the current timetable period in the graphic timetable view is available.

Moved here from #36 (closed) (Handling and displaying operating periods): "Optionally displaying as heading in the graphical timetable viewer".

  1. Take the chosen train. Additionally other trains will be visualized, but not considered for the heading.
  2. Take the first trainPart[@id = train/trainPartSequence[1]/trainPartRef[1]/@ref]
  3. Take the referred timetablePeriod[@id = trainPart/@timetablePeriodRef] if available
  4. Otherwise (@timetablePeriodRef is absent) leave this line blank
  5. Show timetablePeriod/@name if available
  6. Otherwise show timetablePeriod/@description if available
  7. Otherwise show timetablePeriod/@startDate and timetablePeriod/@endDate if available
Edited 2 years ago

    Tasks

    0

    No tasks are currently assigned. Use tasks to break down this issue into smaller parts.

    Linked items
    0

    Link issues together to show that they're related. Learn more.

    Activity


    • R
      Administrator @root · 10 years ago
      Author Owner

      At the railML-timetable-workgroup-meeting (2015-03-16, Vienna) other developers proposed to discard timetablePeriod/@name and timetablePeriod/@description because of free text input by the software user.

      See also #38 (closed) (for train/@name and train/@description)

      Should the same behaviour be implemented? That would mean only 7th item of the list above.

      By Deleted User on 2015-03-25T16:50:15 (imported from GitLab)

    • R
      Administrator @root · 10 years ago
      Author Owner

      The same topic for operatingPeriod/@name, operatingPeriod/@code and operatingPeriod/@description.

      By Deleted User on 2015-03-25T17:01:08 (imported from GitLab)

    • R
      Administrator @root · 10 years ago
      Author Owner
      • Milestone changed from %"4. Meeting" to %"next meeting"

      By Deleted User on 2015-04-09T11:17:09 (imported from GitLab)

    • R
      Administrator @root · 10 years ago
      Author Owner
      • Milestone changed from %"next meeting" to %"Productive version (V1.0)"

      By Deleted User on 2015-05-07T13:53:43 (imported from GitLab)

    • R
      Administrator @root · 10 years ago
      Author Owner

      agreed on project meeting (2015-05-07): for graphic timetable view the same header (timetable period) have to be used like the tabular view

      By Deleted User on 2015-05-07T17:51:51 (imported from GitLab)

    • R
      Administrator @root · 10 years ago
      Author Owner
      • Owner set to @deleted-user
      • Status changed from new to assigned

      By Deleted User on 2015-05-07T17:52:17 (imported from GitLab)

    • R
      Administrator @root · 10 years ago
      Author Owner
      • Milestone %"Productive version (V1.0)" deleted

      • Version changed from 1.0 to 1.1

      • headers don't contain timetable periode so far

      • a special logic is necessary to fit all possible versions to give timetable periods in the file together --> some algorithm are needed

      • in case a consolidated periode is defined, it is not obvious what rules should be implemented to show correct views

      • so far, that can not be solved during version 1.0

      By Deleted User on 2015-06-04T14:49:02 (imported from GitLab)

    • R
      Administrator @root · 9 years ago
      Author Owner
      • Version changed from 1.1 to 1.2

      By Deleted User on 2016-05-22T14:30:43 (imported from GitLab)

    • R
      Administrator @root · 8 years ago
      Author Owner
      • Owner set to @deleted-user
      • Priority changed from normal to minor

      By Coordination on 2017-02-26T20:53:49 (imported from GitLab)

    • R
      Administrator @root · 8 years ago
      Author Owner
      • Owner set to @deleted-user

      By Deleted User on 2017-03-19T14:14:56 (imported from GitLab)

    • R
      Administrator @root · 8 years ago
      Author Owner

      In [changeset:"733/railML-viewer"]:

      see #42 and #43

      By Deleted User on 2017-05-28T15:19:53 (imported from GitLab)

    • Administrator mentioned in commit b78caf3a 3 years ago

      mentioned in commit b78caf3a

      By TT Coordination on 2021-12-15T16:09:06 (imported from GitLab)

    • Organisation changed the description 2 years ago

      changed the description

    • Organisation changed milestone to %2.1 2 years ago

      changed milestone to %2.1

    • Organisation removed 1.0 label 2 years ago

      removed 1.0 label

    • Organisation removed 1.1 label 2 years ago

      removed 1.1 label

    • Organisation removed 1.2 label 2 years ago

      removed 1.2 label

    • Organisation added 2.x label 2 years ago

      added 2.x label

    • Organisation removed normal label 2 years ago

      removed normal label

    Please register or sign in to reply
    Assignee
    Administrator's avatar
    Administrator
    Assign to
    Labels
    0
    None
    0
    None
      Assign labels
    • Manage project labels

    Milestone
    No milestone
    None
    Due date
    None
    None
    None
    Time tracking
    No estimate or time spent
    Confidentiality
    Not confidential
    Not confidential

    You are going to turn on confidentiality. Only project members with at least the Reporter role, the author, and assignees can view or be notified about this issue.

    Lock issue
    Unlocked
    0
    0 Participants
    Reference:

    Menu

    Explore Projects Groups Topics Snippets

    railML.org e.V. (Registry of Associations: VR 5750) Phone: +49 351 47582911 Altplauen 19h; 01187 Dresden; Germany