Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Snippets
  • Sign up now
  • Login
  • Sign in / Register
  • Lazarus Lazarus
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 2,112
    • Issues 2,112
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 14
    • Merge requests 14
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • External wiki
    • External wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • FPC
  • LazarusLazarus
  • LazarusLazarus
  • Issues
  • #35025
Closed
Open
Issue created Feb 06, 2019 by FPC Admin account@fpc_adminOwner

TAChart: potential improvement for marks' direction

Original Reporter info from Mantis: Marcin Wiazowski
  • Reporter name:

Description:

Currently, for series having ZeroLevel (like bar series), when MarkPositions = lmpInside / lmpOutside, data points having their Y = ZeroLevel receive mark's direction arbitrarily set towards +INF (lmpOutside) or -INF (lmpInside).

I successfully modified the code, so in this case mark's direction is calculated by using average level of all data points - exactly as it is now for series not having ZeroLevel (like line series).

Only in case when it still doesn't help (i.e. when Y = average level of all data points), the current arbitrary behavior is used.

Regards

Mantis conversion info:

  • Mantis ID: 35025
  • Build: 60350
  • Version: 2.1 (SVN)
  • Fixed in revision: 60352 (#b96d9fef), r60366 (#f186bca5)
  • Target version: 2.0.2
Assignee
Assign to
Time tracking