Message-ID: <774681306.2099.1711724241096.JavaMail.SALLY$@SALLY> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_2098_322034478.1711724241096" ------=_Part_2098_322034478.1711724241096 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html Navigation Paths

Navigation Paths

Navigation items in the WMC are identified by Navigation Pa= ths. These case-insensitive paths describe the hierarchy of items in relati= on to other items of the same type. The root node of the Navigation Path (c= alled the domain) indicates the type of navigation item.

Domain Description
NAVIGATIONTREE A Navigation Path that identifies an item in the= navigation tree
HELP A Navigation Path that identifies help pan= e content
TASKLIST A Navigation Path that identifies a group = or item in the task list.
MESSAGEBAR A Navigation Path that identifies an item = in the navigation bar at the top of the WMC

Examples:

NAVIGATIONTREE\ControlPane= l\Events refers to the Events item in the navigation= tree that sits under the Control Panel item.

TASKLIST\Data\ResetValue refers to the ta= sk ResetValue that lies under the Data task gro= up.

HELP\NAVIGATIONTREE\ControlPanel\Events refers to = a help item that is automatically associated with the navigation tree item = ControlPanel\Events

 

NavInsertItem takes a = Navigation Path and uses it to create an item at that location. The domain = with which an item lives is defined by the root of the path and levels in t= he hierarchy are specified by the path separator '\'. Paths can effectively= be any depth you wish.

Aliases

Navigation Paths can have aliases. By using aliases the underlying navig= ation path can change and the framework will still be able to find it via i= ts alias. NavInsertItem<= /a> allows you to specify an alias when you add the item. Use the NavI= temHelpers function MakeAliasForName to easily create an alias from a = name.

If you have a component that needs to allow others to know about its nav= igation items (To place tree node under it for instance) then publish the a= lias not the full navigation path. So long as you don't rename the alias th= en you can move/rename the navigation path within the hierarchy and client = code will continue to find your item via its alias.

Like Navigation Paths, aliases are case-insensitive.

 

=20 =20

Qbik highly recommends that you use aliases to find parent items when in= serting your own navigation items. This ensures that your items continue to= operate correctly even when the underlying navigation paths change.

=20
=20
=20 =20

Make sure your alias is unique. Qbik Well known aliases are undecorated but you should ensur= e your alias can be differentiated from someone elses. E.g. Don't call your= alias File, but use something that uniquely identifies your alias= such as MyCompanyScannerComponentFile, mycompany.scanner.file or a str= ing UUID if you wish. MakeAliasFromName(L"703201E2-6ACF-463D-AA4B= -038F99AD9414");

=20
------=_Part_2098_322034478.1711724241096--