Possibly bug with dynamic input field.

> I'm building a form that uses a generic dialog box for data entry.  The
> input field in the dialog box is dynamically bound to an element depending
> on what element the user is wanting to change.  So, in the attached example,
> the variables-instance/EditNode will contain the saxon:path to the actual
> element the user is wishing to modify.  This approach works, and I'm able to
> bind and the display of the field *generally* is correct.  So, if I
> reference an element that has a binding with a type declaration of
> xforms:date, then a date widget appears, and for all other cases a plan text
> box appears.  What I came across today is when I click to modify a field
> that is of type [xforms:date], do something and close down the dialog box,
> and then modify a field of type [xforms:float], the date widget stays.
>  Whats even odder, is when I do the same type of operation but instead click
> on a field of type [text], the date widget disappears.  For some reason, the
> transition from a field of type date to a field of type float does not fully
> work.  I'm at a loss of where to begin to try to help troubleshoot/diagnose
> what may be causing the issue.  For all I know, it might be something with
> how I've designing the page.  I'm going to see if I can find a workaround,
> but thought you may want to research if this is indeed a bug.
>
> Orbeon Version: nightly build (CE edition, 2010-04-19)
> JDK: 1.6.0_18
>
> Attached: xhtml file plus 2 supporting instance data files
>
> --
> ------------------------------------------------------------------------
> Jeremy Nix
> Senior Application Developer
> Cincinnati Children's Hospital Medical Center
>
>
> --
> 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
>
>

> Jeremy,
>
> I inlined the 2 instances in the example you attached, and have your
> example running. But from there how can I reproduce the issue? All the
> fields are disabled in that example?
>
> Alex
>
> On Thu, Apr 22, 2010 at 7:40 AM, Jeremy Nix<[hidden email]>  wrote:
>    
>> I'm building a form that uses a generic dialog box for data entry.  The
>> input field in the dialog box is dynamically bound to an element depending
>> on what element the user is wanting to change.  So, in the attached example,
>> the variables-instance/EditNode will contain the saxon:path to the actual
>> element the user is wishing to modify.  This approach works, and I'm able to
>> bind and the display of the field *generally* is correct.  So, if I
>> reference an element that has a binding with a type declaration of
>> xforms:date, then a date widget appears, and for all other cases a plan text
>> box appears.  What I came across today is when I click to modify a field
>> that is of type [xforms:date], do something and close down the dialog box,
>> and then modify a field of type [xforms:float], the date widget stays.
>>   Whats even odder, is when I do the same type of operation but instead click
>> on a field of type [text], the date widget disappears.  For some reason, the
>> transition from a field of type date to a field of type float does not fully
>> work.  I'm at a loss of where to begin to try to help troubleshoot/diagnose
>> what may be causing the issue.  For all I know, it might be something with
>> how I've designing the page.  I'm going to see if I can find a workaround,
>> but thought you may want to research if this is indeed a bug.
>>
>> Orbeon Version: nightly build (CE edition, 2010-04-19)
>> JDK: 1.6.0_18
>>
>> Attached: xhtml file plus 2 supporting instance data files
>>
>> --
>> ------------------------------------------------------------------------
>> Jeremy Nix
>> Senior Application Developer
>> Cincinnati Children's Hospital Medical Center
>>
>>
>> --
>> 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
>>
>>
>>      
>
>
>    

> Alex,
>
> I've attached a few screen shots to help illustrate what's happening.  When
> the page loads, you should get something that looks like Screenshot1.png.
>  Then, if you were to click on the Modify link next to one of the float
> field values (Total LOS for ex.) you would receive dialog box that looks
> like Screenshot2.png.  Click Apply or Cancel to close the dialog.  Now, if
> you click on the Modify link next to a date field, you will see something
> like Screenshot3.png where a calendar widget appears next to the input
> field.  Again, click Apply or Cancel to close the dialog.  Now go back and
> click on the Modify link next to a float field and you will notice that the
> calendar widget still appears (Screenshot4.png).  I found that I could try
> to use the Modify link dialog with any float field and the calendar widget
> would always appear.  It was not until I used the Modify link dialog with
> the text field (Transplant Number) that the calendar widget would finally
> disappear.
>
> Does that help?
>
> ------------------------------------------------------------------------
> Jeremy Nix
> Senior Application Developer
> Cincinnati Children's Hospital Medical Center
>
> On 04/22/2010 08:01 PM, Alessandro Vernet wrote:
>>
>> Jeremy,
>>
>> I inlined the 2 instances in the example you attached, and have your
>> example running. But from there how can I reproduce the issue? All the
>> fields are disabled in that example?
>>
>> Alex
>>
>> On Thu, Apr 22, 2010 at 7:40 AM, Jeremy Nix<[hidden email]>  wrote:
>>
>>>
>>> I'm building a form that uses a generic dialog box for data entry.  The
>>> input field in the dialog box is dynamically bound to an element
>>> depending
>>> on what element the user is wanting to change.  So, in the attached
>>> example,
>>> the variables-instance/EditNode will contain the saxon:path to the actual
>>> element the user is wishing to modify.  This approach works, and I'm able
>>> to
>>> bind and the display of the field *generally* is correct.  So, if I
>>> reference an element that has a binding with a type declaration of
>>> xforms:date, then a date widget appears, and for all other cases a plan
>>> text
>>> box appears.  What I came across today is when I click to modify a field
>>> that is of type [xforms:date], do something and close down the dialog
>>> box,
>>> and then modify a field of type [xforms:float], the date widget stays.
>>>  Whats even odder, is when I do the same type of operation but instead
>>> click
>>> on a field of type [text], the date widget disappears.  For some reason,
>>> the
>>> transition from a field of type date to a field of type float does not
>>> fully
>>> work.  I'm at a loss of where to begin to try to help
>>> troubleshoot/diagnose
>>> what may be causing the issue.  For all I know, it might be something
>>> with
>>> how I've designing the page.  I'm going to see if I can find a
>>> workaround,
>>> but thought you may want to research if this is indeed a bug.
>>>
>>> Orbeon Version: nightly build (CE edition, 2010-04-19)
>>> JDK: 1.6.0_18
>>>
>>> Attached: xhtml file plus 2 supporting instance data files
>>>
>>> --
>>> ------------------------------------------------------------------------
>>> Jeremy Nix
>>> Senior Application Developer
>>> Cincinnati Children's Hospital Medical Center
>>>
>>>
>>> --
>>> 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
>
>

> Jeremy,
>
> Thank you for the additional instructions. With this, I was able to
> reproduce the issue, and added this bug.
>
> http://forge.ow2.org/tracker/index.php?func=detail&aid=314967&group_id=168&atid=350207
>
> The fix is relatively simple, but before we do this change I'd like to
> have a test case to cover this, which is not entirely trivial to
> create. So fixing this one might take us a bit longer.
>
> Alex
>
> On Fri, Apr 23, 2010 at 3:51 AM, Jeremy Nix <[hidden email]> wrote:
>> Alex,
>>
>> I've attached a few screen shots to help illustrate what's happening.  When
>> the page loads, you should get something that looks like Screenshot1.png.
>>  Then, if you were to click on the Modify link next to one of the float
>> field values (Total LOS for ex.) you would receive dialog box that looks
>> like Screenshot2.png.  Click Apply or Cancel to close the dialog.  Now, if
>> you click on the Modify link next to a date field, you will see something
>> like Screenshot3.png where a calendar widget appears next to the input
>> field.  Again, click Apply or Cancel to close the dialog.  Now go back and
>> click on the Modify link next to a float field and you will notice that the
>> calendar widget still appears (Screenshot4.png).  I found that I could try
>> to use the Modify link dialog with any float field and the calendar widget
>> would always appear.  It was not until I used the Modify link dialog with
>> the text field (Transplant Number) that the calendar widget would finally
>> disappear.
>>
>> Does that help?
>>
>> ------------------------------------------------------------------------
>> Jeremy Nix
>> Senior Application Developer
>> Cincinnati Children's Hospital Medical Center
>>
>> On 04/22/2010 08:01 PM, Alessandro Vernet wrote:
>>>
>>> Jeremy,
>>>
>>> I inlined the 2 instances in the example you attached, and have your
>>> example running. But from there how can I reproduce the issue? All the
>>> fields are disabled in that example?
>>>
>>> Alex
>>>
>>> On Thu, Apr 22, 2010 at 7:40 AM, Jeremy Nix<[hidden email]>  wrote:
>>>
>>>>
>>>> I'm building a form that uses a generic dialog box for data entry.  The
>>>> input field in the dialog box is dynamically bound to an element
>>>> depending
>>>> on what element the user is wanting to change.  So, in the attached
>>>> example,
>>>> the variables-instance/EditNode will contain the saxon:path to the actual
>>>> element the user is wishing to modify.  This approach works, and I'm able
>>>> to
>>>> bind and the display of the field *generally* is correct.  So, if I
>>>> reference an element that has a binding with a type declaration of
>>>> xforms:date, then a date widget appears, and for all other cases a plan
>>>> text
>>>> box appears.  What I came across today is when I click to modify a field
>>>> that is of type [xforms:date], do something and close down the dialog
>>>> box,
>>>> and then modify a field of type [xforms:float], the date widget stays.
>>>>  Whats even odder, is when I do the same type of operation but instead
>>>> click
>>>> on a field of type [text], the date widget disappears.  For some reason,
>>>> the
>>>> transition from a field of type date to a field of type float does not
>>>> fully
>>>> work.  I'm at a loss of where to begin to try to help
>>>> troubleshoot/diagnose
>>>> what may be causing the issue.  For all I know, it might be something
>>>> with
>>>> how I've designing the page.  I'm going to see if I can find a
>>>> workaround,
>>>> but thought you may want to research if this is indeed a bug.
>>>>
>>>> Orbeon Version: nightly build (CE edition, 2010-04-19)
>>>> JDK: 1.6.0_18
>>>>
>>>> Attached: xhtml file plus 2 supporting instance data files
>>>>
>>>> --
>>>> ------------------------------------------------------------------------
>>>> Jeremy Nix
>>>> Senior Application Developer
>>>> Cincinnati Children's Hospital Medical Center
>>>>
>>>>
>>>> --
>>>> 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
>>
>>
>
>
>
> --
> Orbeon Forms - Web forms, open-source, for the Enterprise -
> http://www.orbeon.com/
> My Twitter: http://twitter.com/avernet
>

> Alex,
>
> I've attached a few screen shots to help illustrate what's happening.  When
> the page loads, you should get something that looks like Screenshot1.png.
>  Then, if you were to click on the Modify link next to one of the float
> field values (Total LOS for ex.) you would receive dialog box that looks
> like Screenshot2.png.  Click Apply or Cancel to close the dialog.  Now, if
> you click on the Modify link next to a date field, you will see something
> like Screenshot3.png where a calendar widget appears next to the input
> field.  Again, click Apply or Cancel to close the dialog.  Now go back and
> click on the Modify link next to a float field and you will notice that the
> calendar widget still appears (Screenshot4.png).  I found that I could try
> to use the Modify link dialog with any float field and the calendar widget
> would always appear.  It was not until I used the Modify link dialog with
> the text field (Transplant Number) that the calendar widget would finally
> disappear.
>
> Does that help?
>
> ------------------------------------------------------------------------
> Jeremy Nix
> Senior Application Developer
> Cincinnati Children's Hospital Medical Center
>
> On 04/22/2010 08:01 PM, Alessandro Vernet wrote:
>>
>> Jeremy,
>>
>> I inlined the 2 instances in the example you attached, and have your
>> example running. But from there how can I reproduce the issue? All the
>> fields are disabled in that example?
>>
>> Alex
>>
>> On Thu, Apr 22, 2010 at 7:40 AM, Jeremy Nix<[hidden email]>  wrote:
>>
>>>
>>> I'm building a form that uses a generic dialog box for data entry.  The
>>> input field in the dialog box is dynamically bound to an element
>>> depending
>>> on what element the user is wanting to change.  So, in the attached
>>> example,
>>> the variables-instance/EditNode will contain the saxon:path to the actual
>>> element the user is wishing to modify.  This approach works, and I'm able
>>> to
>>> bind and the display of the field *generally* is correct.  So, if I
>>> reference an element that has a binding with a type declaration of
>>> xforms:date, then a date widget appears, and for all other cases a plan
>>> text
>>> box appears.  What I came across today is when I click to modify a field
>>> that is of type [xforms:date], do something and close down the dialog
>>> box,
>>> and then modify a field of type [xforms:float], the date widget stays.
>>>  Whats even odder, is when I do the same type of operation but instead
>>> click
>>> on a field of type [text], the date widget disappears.  For some reason,
>>> the
>>> transition from a field of type date to a field of type float does not
>>> fully
>>> work.  I'm at a loss of where to begin to try to help
>>> troubleshoot/diagnose
>>> what may be causing the issue.  For all I know, it might be something
>>> with
>>> how I've designing the page.  I'm going to see if I can find a
>>> workaround,
>>> but thought you may want to research if this is indeed a bug.
>>>
>>> Orbeon Version: nightly build (CE edition, 2010-04-19)
>>> JDK: 1.6.0_18
>>>
>>> Attached: xhtml file plus 2 supporting instance data files
>>>
>>> --
>>> ------------------------------------------------------------------------
>>> Jeremy Nix
>>> Senior Application Developer
>>> Cincinnati Children's Hospital Medical Center
>>>
>>>
>>> --
>>> 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
>
>

> Jeremy,
>
> This is now fixed. I just pushed the fix as well a unit test to
> GitHub, and it will be included in the next nightly build. You'll let
> me know if this works for you.
>
> Alex
>
> On Fri, Apr 23, 2010 at 3:51 AM, Jeremy Nix<[hidden email]>  wrote:
>    
>> Alex,
>>
>> I've attached a few screen shots to help illustrate what's happening.  When
>> the page loads, you should get something that looks like Screenshot1.png.
>>   Then, if you were to click on the Modify link next to one of the float
>> field values (Total LOS for ex.) you would receive dialog box that looks
>> like Screenshot2.png.  Click Apply or Cancel to close the dialog.  Now, if
>> you click on the Modify link next to a date field, you will see something
>> like Screenshot3.png where a calendar widget appears next to the input
>> field.  Again, click Apply or Cancel to close the dialog.  Now go back and
>> click on the Modify link next to a float field and you will notice that the
>> calendar widget still appears (Screenshot4.png).  I found that I could try
>> to use the Modify link dialog with any float field and the calendar widget
>> would always appear.  It was not until I used the Modify link dialog with
>> the text field (Transplant Number) that the calendar widget would finally
>> disappear.
>>
>> Does that help?
>>
>> ------------------------------------------------------------------------
>> Jeremy Nix
>> Senior Application Developer
>> Cincinnati Children's Hospital Medical Center
>>
>> On 04/22/2010 08:01 PM, Alessandro Vernet wrote:
>>      
>>> Jeremy,
>>>
>>> I inlined the 2 instances in the example you attached, and have your
>>> example running. But from there how can I reproduce the issue? All the
>>> fields are disabled in that example?
>>>
>>> Alex
>>>
>>> On Thu, Apr 22, 2010 at 7:40 AM, Jeremy Nix<[hidden email]>    wrote:
>>>
>>>        
>>>> I'm building a form that uses a generic dialog box for data entry.  The
>>>> input field in the dialog box is dynamically bound to an element
>>>> depending
>>>> on what element the user is wanting to change.  So, in the attached
>>>> example,
>>>> the variables-instance/EditNode will contain the saxon:path to the actual
>>>> element the user is wishing to modify.  This approach works, and I'm able
>>>> to
>>>> bind and the display of the field *generally* is correct.  So, if I
>>>> reference an element that has a binding with a type declaration of
>>>> xforms:date, then a date widget appears, and for all other cases a plan
>>>> text
>>>> box appears.  What I came across today is when I click to modify a field
>>>> that is of type [xforms:date], do something and close down the dialog
>>>> box,
>>>> and then modify a field of type [xforms:float], the date widget stays.
>>>>   Whats even odder, is when I do the same type of operation but instead
>>>> click
>>>> on a field of type [text], the date widget disappears.  For some reason,
>>>> the
>>>> transition from a field of type date to a field of type float does not
>>>> fully
>>>> work.  I'm at a loss of where to begin to try to help
>>>> troubleshoot/diagnose
>>>> what may be causing the issue.  For all I know, it might be something
>>>> with
>>>> how I've designing the page.  I'm going to see if I can find a
>>>> workaround,
>>>> but thought you may want to research if this is indeed a bug.
>>>>
>>>> Orbeon Version: nightly build (CE edition, 2010-04-19)
>>>> JDK: 1.6.0_18
>>>>
>>>> Attached: xhtml file plus 2 supporting instance data files
>>>>
>>>> --
>>>> ------------------------------------------------------------------------
>>>> Jeremy Nix
>>>> Senior Application Developer
>>>> Cincinnati Children's Hospital Medical Center
>>>>
>>>>
>>>> --
>>>> 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
>>
>>
>>      
>
>
>    

> Alex,
>
> The fix worked like a charm.  Thanks for the help.
>
> ------------------------------------------------------------------------
> Jeremy Nix
> Senior Application Developer
> Cincinnati Children's Hospital Medical Center
>
> On 05/04/2010 08:24 PM, Alessandro Vernet wrote:
>>
>> Jeremy,
>>
>> This is now fixed. I just pushed the fix as well a unit test to
>> GitHub, and it will be included in the next nightly build. You'll let
>> me know if this works for you.
>>
>> Alex
>>
>> On Fri, Apr 23, 2010 at 3:51 AM, Jeremy Nix<[hidden email]>  wrote:
>>
>>>
>>> Alex,
>>>
>>> I've attached a few screen shots to help illustrate what's happening.
>>>  When
>>> the page loads, you should get something that looks like Screenshot1.png.
>>>  Then, if you were to click on the Modify link next to one of the float
>>> field values (Total LOS for ex.) you would receive dialog box that looks
>>> like Screenshot2.png.  Click Apply or Cancel to close the dialog.  Now,
>>> if
>>> you click on the Modify link next to a date field, you will see something
>>> like Screenshot3.png where a calendar widget appears next to the input
>>> field.  Again, click Apply or Cancel to close the dialog.  Now go back
>>> and
>>> click on the Modify link next to a float field and you will notice that
>>> the
>>> calendar widget still appears (Screenshot4.png).  I found that I could
>>> try
>>> to use the Modify link dialog with any float field and the calendar
>>> widget
>>> would always appear.  It was not until I used the Modify link dialog with
>>> the text field (Transplant Number) that the calendar widget would finally
>>> disappear.
>>>
>>> Does that help?
>>>
>>> ------------------------------------------------------------------------
>>> Jeremy Nix
>>> Senior Application Developer
>>> Cincinnati Children's Hospital Medical Center
>>>
>>> On 04/22/2010 08:01 PM, Alessandro Vernet wrote:
>>>
>>>>
>>>> Jeremy,
>>>>
>>>> I inlined the 2 instances in the example you attached, and have your
>>>> example running. But from there how can I reproduce the issue? All the
>>>> fields are disabled in that example?
>>>>
>>>> Alex
>>>>
>>>> On Thu, Apr 22, 2010 at 7:40 AM, Jeremy Nix<[hidden email]>
>>>>  wrote:
>>>>
>>>>
>>>>>
>>>>> I'm building a form that uses a generic dialog box for data entry.  The
>>>>> input field in the dialog box is dynamically bound to an element
>>>>> depending
>>>>> on what element the user is wanting to change.  So, in the attached
>>>>> example,
>>>>> the variables-instance/EditNode will contain the saxon:path to the
>>>>> actual
>>>>> element the user is wishing to modify.  This approach works, and I'm
>>>>> able
>>>>> to
>>>>> bind and the display of the field *generally* is correct.  So, if I
>>>>> reference an element that has a binding with a type declaration of
>>>>> xforms:date, then a date widget appears, and for all other cases a plan
>>>>> text
>>>>> box appears.  What I came across today is when I click to modify a
>>>>> field
>>>>> that is of type [xforms:date], do something and close down the dialog
>>>>> box,
>>>>> and then modify a field of type [xforms:float], the date widget stays.
>>>>>  Whats even odder, is when I do the same type of operation but instead
>>>>> click
>>>>> on a field of type [text], the date widget disappears.  For some
>>>>> reason,
>>>>> the
>>>>> transition from a field of type date to a field of type float does not
>>>>> fully
>>>>> work.  I'm at a loss of where to begin to try to help
>>>>> troubleshoot/diagnose
>>>>> what may be causing the issue.  For all I know, it might be something
>>>>> with
>>>>> how I've designing the page.  I'm going to see if I can find a
>>>>> workaround,
>>>>> but thought you may want to research if this is indeed a bug.
>>>>>
>>>>> Orbeon Version: nightly build (CE edition, 2010-04-19)
>>>>> JDK: 1.6.0_18
>>>>>
>>>>> Attached: xhtml file plus 2 supporting instance data files
>>>>>
>>>>> --
>>>>>
>>>>> ------------------------------------------------------------------------
>>>>> Jeremy Nix
>>>>> Senior Application Developer
>>>>> Cincinnati Children's Hospital Medical Center
>>>>>
>>>>>
>>>>> --
>>>>> 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
>>>
>>>
>>>
>>
>>
>>
>
>
> --
> 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
>
>