Difference between revisions of "Resolving Task Bar Name Label Collisions for Version 7.2 (Portal)"

Latest revision as of 16:58, 9 January 2024

Introduction

Illustrations used in this article are from OnePager Pro using data from Microsoft Project but the features, function, controls, and manual edits apply equally to other OnePager editions that import from data sources like Microsoft Excel, Microsoft Project for the Web, Smartsheet, Oracle Primavera P6, Planisware Enterprise, Asana, and Wrike.

This article describes OnePager’s Task Bar Name Label Collision Avoidance feature.

Overview

For the purpose of this discussion, a task bar name label is the Task Name field imported from Microsoft Project, Microsoft Excel , Oracle Primavera P6, or Smartsheet and typically used in a OnePager Pro, OnePager Express, or OnePager Bundle chart to denote that imported Task/Milestone Name associated with a task bar or milestone symbol. Previous versions of OnePager required you to manually re-position task bar name labels for Task Names in the chart when various editing actions caused task bar name labels to overlay or be hidden by other task bars or milestone symbols. Under such conditions the task bar name labels are said to collide and the purpose of this feature is to give you automatic and manual capabilities to resolve task bar name label collisions in the graph that look like this before resolution:

When a task bar name label overlays a task bar or other task bar name label they become difficult to read in the chart or other output media. The Smart Text Optimization feature is intended to help you resolve task bar name label collision situations without resorting to numerous editing actions in the Chart Editor. The Smart Text Optimization feature recognizes these task name label collision situations during chart UPDATES and automatically attempts to take the task bar name labels involved out of collision.

In OnePager Pro, OnePager Express, and OnePager Bundle, we changed the selection options for task bars and task bar name labels by separating them into two distinct left-click selections such that you can now select only a task bar/milestone symbol or their task bar name label. To provide continuity with previous versions of OnePager, a checkbox is provided in the Template Properties and Chart Properties form’s Advanced tabs to revert to the selection options available in previous versions as shown here for the Chart Properties form's Advanced tab:

For depth information on Smart Text Optimization, please see the article at the link given below:

Smart Text Optimization

Implementation of the Smart Text Optimization feature comes with three (3) additional task bar name label position options: Best fit all directions, Best fit above/below, Legacy best fit. The Legacy best fit option recognizes task bar name label positions from previous versions of OnePager Pro and OnePager Express and utilizes those positions when creating a OnePager Pro or OnePager Express chart. The new task bar name label positions are shown below:

Within the Template Properties and Chart Properties form’s Task Bars and Milestones tabs is a redesigned form providing you with controls to operate the algorithm used to make automatic decisions for resolving task bar name label collisions as shown below:

Provided with this redesigned form are a set of controls that give you options for establishing the priorities with which the algorithm, called the text collision avoidance algorithm, employs the feature for you. Additionally there are two controls that provide you with the capability to adjust the sensitivity of the text collision avoidance algorithm in the vertical and horizontal directions.

Finally, there are new commands provided in the task bar right-click context menu and the task bar name label right-click context menu you can use to perform the text collision avoidance algorithm manually on selected task bars that are involved in a task name label collision situation as shown in the two illustrations that follow:

For depth information on Smart Text Optimization, please see the article at the link given below:

Related Links

(9.7.1-72)