Navigators are nice for restricting the end users' feature set; however, if you support databases that always open to custom navigators with a standard view, you may face an inconvenience when working with it as the developer.
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
Most of the time, when you as the developer open the database, you don't want to be encumbered by the end-user's custom navigator and standard view. You are forced to either build in database code that recognizes your access level and doesn't open the custom navigator, or you have to do a "View>Go to" to get into the database with the standard Views/Folder navigator. Another option is to embed a hidden hotspot in the custom navigator that does this.
However, all of these are very specific to the particular database, and may involve additional mouse-clicks. I discovered that a simple one-line command can be used on a SmartIcon to simplify this admittedly trivial but still annoying aspect of day-to-day development.
Add a SmartIcon with nothing in it but "@Command([OpenView])". What is nice is that the SmartIcon will work even without opening the database first. This is not true of the command "ViewNavigatorsFolders", which only works when the database is already open.
By clicking on a database icon, then clicking the SmartIcon, the database opens to the navigators or folders view. It opens to the last view you had open, even if it is a hidden view. This is normal for Notes if the database isn't launching into a standard navigator and view, but those databases are not a problem anyway.
I have found this to be a real timesaver. It works with any database, so no custom code is needed.