Navigating Map views

Why do some icons look different?

Although the actual color of each note's icon in a Map View may vary by the color-related attributes you set, it will always appear in one of two basic styles:

• Notes without children. A solid block of color Color with at note title in contrasting black or white text.
• Notes with children. These also have a section of solid color at the top with the note title but in addition the icon is extended vertically and a grey area inset into it, referred to below as the 'viewport'. Notes in this state are described as 'containers'.

What are the blocks of color in the grey area of the container notes?

These represent child notes inside the container, i.e. you are seeing down one level into the the child notes' map. By default the child notes in the viewport will show their titles as well. If the sub-map in the viewport doesn't have a grey background that is because it's MapBackgroundColor has been set to a non-default value.

Why is the grey area at the top of some containers and not the bottom?

These indicate the container is an agent. To clarify, in a Map view a normal note container has its title area at the top of the note whilst an agent container has its title area at the bottom of the note.

How do I navigate down / open a container / drill down a level?

The three preceding questions are effectively all the same. To drill down into any container, you double-click the viewport area of the note and you then navigate down / open / drill down — whichever euphemism you prefer. Should you mistakenly click the top (title) part of the note icon you'll open the note for editing. If the latter happens by mistake, don't worry, simply close the note and make sure you double-click the lower portion of the note. This method works for both normal (note) and agent containers.

Can I interact with the child map in the viewport?

Yes you may thought it often helps to drag the parent containers icon ia bit larger to increase the size of the viewport. You can do two things:

• 'Scroll' the child map. To do this click onto any background area of the child map, i.e. not on a note/container icon, and drag. This will scroll the child map within the parent's viewport. A container's viewport will remember the section of the last-used (visible) section of the map. The data is stored in the attributes MapScrollX and MapScrollY.
• Promote notes/containers from the child map to the current map. Simply click on the note or agent in the child map and drag it out of the viewport onto the parent map.
• Demoting note/containers from the current map to the child map. Click on the note or agent in the current map and drag it into a container's viewport.

Can containers show note body copy text, display tabular info, etc., like non-containers?

Yes. For containers, note or agent, the attribute TitleHeight controls how much of the map icon is devoted to the viewport. The only difference between note and agent containers in this regard is that body text or TableHeading/TableExpression information is always displayed beneath the icon title - which makes sense when you see it on screen - regardless of the relative position of the viewport. To set TitleHeight manually in map view, simple drag the bottom (note container) or top (agent) of the solid color area of the icon and drag it up/down to alter the relative allocation of space to title/text vs. viewport. To provide more space overall drag the corner of the container's note icon; as the icon grows/shrinks in size, the title/viewport allocation scales accordingly allowing the TitleHeight to then be re-adjusted. Being an attribute, TitleHeight can also be set via action code.

Licensed under Creative Commons Attribution-Noncommercial-Share Alike 3.0 License
[See aTbRef CC licence Attribution/Waiver info info]