Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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 level subpath of the path and levels in the hierarchy are specified by the path separator '\'. Paths can effectively be any depth you wish.

...

Navigation Paths can have aliases that are immutable references to navigation paths. By . By using aliases the underlying navigation path can change and the framework will still be able to find it via its alias. NavInsertItem allows you to specify an alias when you add the item and by convention aliases are names surrounded by { } characters. Use the NavItemHelpers function MakeAliasForName to easily create an alias from a name.

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

...

Note

Make sure your alias is unique. Qbik Well known aliases are undecorated but you should ensure 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 string UUID if you wish. MakeAliasFromName(L"703201E2-6ACF-463D-AA4B-038F99AD9414");