Closed thomasds closed 8 years ago
Can you describe what you mean more? It's expecting something like "#page2" if the name of another page is 'page2'.
That is probably what he means grgustaf. There is no autocompletion (dropdown) for the "Target" property under "List Button Properties" inside lists and unordered lists. It is expected to behave the same way as "Button Properties"
I found a similar issue even though there is a dropdown for a Navbar button, selecting say #page2 as an existing page doesn't seem to work. As a work around type in the page name without the # first. Then go back and add the #. Works for me.
jleviaguirre, I see what you're talking about on the 'online' version of RIB at http://01.org/rib, but in the latest code in the tree, the list implementation has changed and that dropdown does let you select existing pages. Is that where you were looking?
72degrees, I don't see the problem you're describing, on either the online version of the github tips.
Hello grgustaf,
Here is how to replicate the situation we are talking about (lack of auto-completion feature on unordered or ordered list button):
In this last step we are expecting to see a drop down list of available pages, the same way you do when adding regular buttons. The lack of the dropwdown showing the pages does not prevent to put the page name manually and make the button work as expected.
I am using Chrome Version 30.0.1599.101 m on Windows Vista (and also tested in a recent version of chrome/W7)
Were you able to replicate it?
OK. So I'm running RIB Version Preview-2 using a localhost WAMP stack on a W7 with Chrome Version 30.0.1599.101 m.
If I create a new page and try to link to it from a button (just a plain vanilla button within a div data-role="content" on any other page), when I click on [target] I do actually get a dropdown offering say #page2. Clicking on that, however, does not update the code for the button. I have to type in the page reference. I shouldn't grumble really though as RIB has still saved me loads of time.
Sorry that I dropped this issue, but we just got a nice one-line patch from @MikeMaxFR that fixed it. It's merged into master.
The interface builder won't let me set the button target