Menu strange behaviour

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Menu strange behaviour

Tony Mobbs
I'm having a problem with the sample application for menus is located at:

http://wiki.orbeon.com/forms/how-to/view/contextual-menu

Selecting an item from the first of the three menu method button produces a
different outcome to selecting the second or third menu buttons.

For example, the first button
Click California -> Result = Maryland
Click Maryland -> Result = Virginia
Click Virginia -> Result = No selection

Using the second or third buttons gives the expected result.

Click California -> Result = California
Click Maryland -> Result = Maryland
Click Virginia -> Result = Virginia

I'm using version 3.9.0.201105152046 CE

Thanks
Tony


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Menu strange behaviour

Alessandro  Vernet
Administrator
Hi Tony,

Good catch. This is now fixed in the latest nightly build, and we also improved the way itemsets are sent from the server to the client. You'll let us know if this works for you.

Alex
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet
Reply | Threaded
Open this post in threaded view
|

Re: Re: Menu strange behaviour

Tony Mobbs
Alex

Thanks for the update.  The new nightly build correctly selects the menu item.

There is however a second issue that I've now identified, in that you can't dynamically select the instance to use.  For example

This works (xxforms:menu with fixed menu selection)
<xforms:select1 ref="instance('Administration')//CurrentSection" appearance="xxforms:menu">
 <xforms:itemset nodeset="instance('DropDowns')//menus[@role='employee']/section/(.,*)">

This works also (minimal with dynamic instance)
 <xforms:select1 class="redSansBold" ref="instance('Administration')//CurrentSection" appearance="minimal">
<xforms:itemset nodeset="instance('DropDowns')//menus[@role=instance('Administration')//role]/section/(.,*)">

But this does not work (xxforms:menu with dynamic instance)
<xforms:select1 ref="instance('Administration')//CurrentSection" appearance="xxforms:menu">
 <xforms:itemset nodeset="instance('DropDowns')//menus[@role=instance('Administration')//role]/section/(.,*)">

Thanks again for your assistance.
Tony


On 28 May 2011 03:19, Alessandro Vernet <[hidden email]> wrote:
Hi Tony,

Good catch. This is now fixed in the latest nightly build, and we also
improved the way itemsets are sent from the server to the client. You'll let
us know if this works for you.

Alex

--
View this message in context: http://orbeon-forms-ops-users.24843.n4.nabble.com/Menu-strange-behaviour-tp3541903p3555879.html
Sent from the Orbeon Forms (ops-users) mailing list archive at Nabble.com.


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws




--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws
Reply | Threaded
Open this post in threaded view
|

Re: Re: Menu strange behaviour

Alessandro  Vernet
Administrator
Hi Tony,

I don't see why your third case of <xforms:select1> wouldn't work. Would you be able to create a minimal, stand-alone XForms file that we can use to reproduce this?

Alex
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet
Reply | Threaded
Open this post in threaded view
|

Re: Re: Re: Menu strange behaviour

Tony Mobbs
Alex

As requested, a stand-alone file that reproduces the issue with <xforms:select1 ... appearance="xxforms:menu">

Cheers
Tony



On 31 May 2011 16:39, Alessandro Vernet <[hidden email]> wrote:
Hi Tony,

I don't see why your third case of <xforms:select1> wouldn't work. Would you
be able to create a minimal, stand-alone XForms file that we can use to
reproduce this?

Alex

--
View this message in context: http://orbeon-forms-ops-users.24843.n4.nabble.com/Menu-strange-behaviour-tp3541903p3562394.html
Sent from the Orbeon Forms (ops-users) mailing list archive at Nabble.com.


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws




--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

example.xml (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Re: Re: Menu strange behaviour

Alessandro  Vernet
Administrator
Hi Tony,

I see; and thank you for the test case. This is because updates to the itemset for menus are not supported at this point (they are the tree and all the other select/select1 appearances). I just checked in a fix so at least you wouldn't get a JavaScript error when this happens. I.e., the menu won't update based on the new itemset, but at least the page will keep working.

Alex
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet
Reply | Threaded
Open this post in threaded view
|

Re: Re: Re: Re: Menu strange behaviour

Tony Mobbs
Thanks Alex

I've checked the nightly build and no errors are produced.

I've tried to achieve the same effect by wrapping menus within groups to hide and show them as required.  Unfortunately the groups won't hide or reveal the menus as desired.  I've prepared an example file showing the issue.

Thanks again for your help

Tony




On 3 June 2011 12:21, Alessandro Vernet <[hidden email]> wrote:
Hi Tony,

I see; and thank you for the test case. This is because updates to the
itemset for menus are not supported at this point (they are the tree and all
the other select/select1 appearances). I just checked in a fix so at least
you wouldn't get a JavaScript error when this happens. I.e., the menu won't
update based on the new itemset, but at least the page will keep working.

Alex

--
View this message in context: http://orbeon-forms-ops-users.24843.n4.nabble.com/Menu-strange-behaviour-tp3541903p3569860.html
Sent from the Orbeon Forms (ops-users) mailing list archive at Nabble.com.


--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws




--
You receive this message as a subscriber of the [hidden email] mailing list.
To unsubscribe: mailto:[hidden email]
For general help: mailto:[hidden email]?subject=help
OW2 mailing lists service home page: http://www.ow2.org/wws

example2.xml (3K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Re: Re: Re: Menu strange behaviour

Alessandro  Vernet
Administrator
Hi Tony,

Unfortunately, non-relevant menus are not supported. I added a bug for this:

http://forge.ow2.org/tracker/index.php?func=detail&aid=316042&group_id=168&atid=350207

As you can see, menus are aren't used in a very sophisticated way by the community. In most cases people have one menu, which doesn't change after the page is loaded. It can be "dynamic" in the sense that it contains different things at a different times, but is fixed after a page is sent to the browser. Maybe you can get around this by using a submission replace="all" pointing to the same page, to force the HTML to be reloaded when the menu needs to change.

Alex
--
Follow Orbeon on Twitter: @orbeon
Follow me on Twitter: @avernet