Screen paths can now start with a // and be a sparse path where each
    name in the path is searched for in the subscreen hierarchy from the
    root screen; can also find content this way; note that this may
    involve loading a lot of screen definitions and in dev mode will be
    a LOT slower, but in production (cache timeouts turned off) the full
    expanded path is cached as are the screen definitions so there is very
    little overhead