• Navigator state "reloaded"

    By miguel calvo 1 decade ago

    Hi,

       I had a problem with keeping the state in a Navigator (expanded and collapsed nodes) based in a beanTreeNode. The last release provided a new property in the Navigator control, keepState. It solves the problem with partial and full refreshes, but it doesn't work if you issue a new URL ( that's the default behaviour if you open a document from a DataView control, so you lose the Navigator state every time you open a document )

      Is there a workaround to keep the navigator state between new URL's petitions ?

     Thanks in advance,

    • Sample NSF would be good

      By Andrejus Chaliapinas 1 decade ago

      Hi Miguel,

      Could you prepare very simple NSF with 1-2 docs in it to demonstrate such problem? I need to look then at that to see how that state keeping logic could be enhanced further.

      • i attach an example

        By miguel calvo 1 decade ago

        Hi,

           The problem can be reproduced:

        1. Open the application in the browser

        2. Change any option in the navigator

        3. Click in any document in the view

        RESULTS

        A new document is shown in the XPAge UI, but the navigator has been reset to its initial state. 

         

        Thank you,