Orbeon Forms community mailing list

old instance data coming back to a page -- version 3.0.beta3.200511020401

Classic

List

Threaded

25 messages Options

Alessandro Vernet

Re: old instance data coming back to a page -- version 3.0.beta3.200511020401

Administrator

Hi Ryan,

It should work out of the box without having to call this method. I
have created a standalone example that you can run in the sandbox that
shows how this works. The example is attached to this email.

Note that the element that has the id you used in XForms will be a
span, not the input field - and this is how it is supposed to be. Have
a look at the example, and if this is what you are doing and it does
not work for you, there is somewhere an issue we need to figure out.

Alex

On 11/18/05, Ryan Puddephatt <[hidden email]> wrote:

> Hi Erik & Alex,
> I have found a little work around, by calling the
> Xforms-dispatchEvent function after changing the value I have managed to
> update the instance. Would this be the only way of doing it or could it be
> included in OPS?
>
> Thanks
>
> Ryan Puddephatt
> Web Developer
> TFX Group
> 1 Michaelson Square
> Livingston
> West Lothian
> Scotand
> EH54 7DP
>
> * [hidden email]
> ( 01506 407 110
> 7 01506 407 108
>
>
> -----Original Message-----
> From: Ryan Puddephatt [mailto:[hidden email]]
> Sent: 17 November 2005 16:39
> To: [hidden email]
> Subject: RE: [ops-users] old instance data coming back to a page -- version
> 3.0.beta3.200511020401
>
> Thanks Erik, sorry was rather misleading at first! We do use the code as you
> suggested to set the value, but it doesn't appear to be setting the
> instance. Looking at Logging Events, OPS doesn't appear to notice the
> change, could I run something in JavaScript to alert OPS to the change? Or
> is it just a bug?
>
> Thanks
>
> Ryan Puddephatt
> Web Developer
> TFX Group
> 1 Michaelson Square
> Livingston
> West Lothian
> Scotand
> EH54 7DP
>
> * [hidden email]
> ( 01506 407 110
> 7 01506 407 108
>
>
> -----Original Message-----
> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
> Sent: 17 November 2005 16:30
> To: [hidden email]
> Subject: Re: [ops-users] old instance data coming back to a page -- version
> 3.0.beta3.200511020401
>
> Ryan Puddephatt wrote:
>
> > I'm not trying to change the value of the id with JavaScript
>
> Sorry, I misunderstood because your sentence was a little misleading:
>
> "[...] the JavaScript [...] doesn't seem to be setting the ID of the
> html:input control"
>
> > <span id="facilityID" class="xforms-control xforms-input"><span
> > class="xforms-date-display"></span><input type="text" name="facilityID"
> > value="" class="xforms-type-string"><span class="xforms-showcalendar
> > xforms-type-string"></span></span>
>
> Yes, that's still a feature, not a bug ;-)
>
> > Alex said we would be able to set the id of the input control.
>
> I think what he said is that you would be able to set the value of the
> control by doing something like (Alex, can you check this?):
>
> getElementById(id).value = myValue;
>
> This does not necessarily imply moving the id to the HTML <input>
> element...
>
> > Also I have made a small work around for the time being, but the
> > instance value of 'summaryUnderPointInFinancialTreeID' is not being
> > changed even though the value of the control has changed via
> > JavaScript
> >
> > So both bugs still appear to be there
>
> I think Alex should be able to confirm the following:
>
> 1) What Javascript syntax is supposed to work to update the value of
> the control.
>
> 2) Whether setting the value in fact causes it to be set in the
> instance - there may be a bug here.
>
> -Erik
>
>
>
>
>
>
>
>
> --
> 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
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
>

--
Blog (XML, Web apps, Open Source): http://www.orbeon.com/blog/

--
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
ObjectWeb mailing lists service home page: http://www.objectweb.org/wws

input-javascript.xhtml (2K) Download Attachment

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

Ryan Puddephatt

RE: old instance data coming back to a page -- version 3.0.beta3.200511020401

Alex, I've run the page and it correctly works, but it doesn't appear to
change the instance data. I've checked the logging events and nothing shows
up. Also when I look at the source for your page I see

<input type="text" name="$portlet$p1.input" value="" id="input"
class="xforms-control xforms-incremental">

Whereas mine looked like

<span id="input"> <input type="text" name="$portlet$p1.input" value=""
name="input" class="xforms-control xforms-incremental"></span>

I fixed this by searching for names to set the value and running the
dispatchevent function to update the instance, we had previously been using
a similar JavaScript to you to get the element!

Any Ideas

Ryan Puddephatt
Web Developer
TFX Group
1 Michaelson Square
Livingston
West Lothian
Scotand
EH54 7DP

* [hidden email]
( 01506 407 110
7 01506 407 108

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Alessandro
Vernet
Sent: 19 November 2005 00:14
To: [hidden email]
Subject: Re: [ops-users] old instance data coming back to a page -- version
3.0.beta3.200511020401

Hi Ryan,

It should work out of the box without having to call this method. I
have created a standalone example that you can run in the sandbox that
shows how this works. The example is attached to this email.

Note that the element that has the id you used in XForms will be a
span, not the input field - and this is how it is supposed to be. Have
a look at the example, and if this is what you are doing and it does
not work for you, there is somewhere an issue we need to figure out.

Alex

On 11/18/05, Ryan Puddephatt <[hidden email]> wrote:

version
> 3.0.beta3.200511020401
>
> Thanks Erik, sorry was rather misleading at first! We do use the code as

you

> suggested to set the value, but it doesn't appear to be setting the
> instance. Looking at Logging Events, OPS doesn't appear to notice the
> change, could I run something in JavaScript to alert OPS to the change? Or
> is it just a bug?
>
> Thanks
>
> Ryan Puddephatt
> Web Developer
> TFX Group
> 1 Michaelson Square
> Livingston
> West Lothian
> Scotand
> EH54 7DP
>
> * [hidden email]
> ( 01506 407 110
> 7 01506 407 108
>
>
> -----Original Message-----
> From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
> Sent: 17 November 2005 16:30
> To: [hidden email]
> Subject: Re: [ops-users] old instance data coming back to a page --

version

> 3.0.beta3.200511020401
>
> Ryan Puddephatt wrote:
>
> > I'm not trying to change the value of the id with JavaScript
>
> Sorry, I misunderstood because your sentence was a little misleading:
>
> "[...] the JavaScript [...] doesn't seem to be setting the ID of the
> html:input control"
>
> > <span id="facilityID" class="xforms-control xforms-input"><span
> > class="xforms-date-display"></span><input type="text" name="facilityID"
> > value="" class="xforms-type-string"><span class="xforms-showcalendar
> > xforms-type-string"></span></span>
>
> Yes, that's still a feature, not a bug ;-)
>
> > Alex said we would be able to set the id of the input control.
>
> I think what he said is that you would be able to set the value of the
> control by doing something like (Alex, can you check this?):
>
> getElementById(id).value = myValue;
>
> This does not necessarily imply moving the id to the HTML <input>
> element...
>
> > Also I have made a small work around for the time being, but the
> > instance value of 'summaryUnderPointInFinancialTreeID' is not being
> > changed even though the value of the control has changed via
> > JavaScript
> >
> > So both bugs still appear to be there
>
> I think Alex should be able to confirm the following:
>
> 1) What Javascript syntax is supposed to work to update the value of
> the control.
>
> 2) Whether setting the value in fact causes it to be set in the
> instance - there may be a bug here.
>
> -Erik
>
>
>
>
>
>
>
>
> --
> 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
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
>

Alessandro Vernet

Re: old instance data coming back to a page -- version 3.0.beta3.200511020401

Administrator

Ryan,

If you don't see the <span> around the <input> in the generated HTML,
you are most likely not running the latest version of OPS, or a
version that has not been completely updated.

We are now generating this span as the <xforms:input> can appear as
some text with a data picker or as a text field depending on the type
of the node bound to the <xforms:input>. We generate those two
possible forms and can switch at runtime using JavaScript as the type
of the node can change after the page is displayed.

Did you update the content of your resources/ops when getting the
latest "unstable build"?

Alex

On 11/19/05, Ryan Puddephatt <[hidden email]> wrote:

> Alex, I've run the page and it correctly works, but it doesn't appear to
> change the instance data. I've checked the logging events and nothing shows
> up. Also when I look at the source for your page I see
>
> <input type="text" name="$portlet$p1.input" value="" id="input"
> class="xforms-control xforms-incremental">
>
> Whereas mine looked like
>
> <span id="input"> <input type="text" name="$portlet$p1.input" value=""
> name="input" class="xforms-control xforms-incremental"></span>
>
> I fixed this by searching for names to set the value and running the
> dispatchevent function to update the instance, we had previously been using
> a similar JavaScript to you to get the element!
>
> Any Ideas
>
> Ryan Puddephatt
> Web Developer
> TFX Group
> 1 Michaelson Square
> Livingston
> West Lothian
> Scotand
> EH54 7DP
>
> * [hidden email]
> ( 01506 407 110
> 7 01506 407 108
>
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of Alessandro
> Vernet
> Sent: 19 November 2005 00:14
> To: [hidden email]
> Subject: Re: [ops-users] old instance data coming back to a page -- version
> 3.0.beta3.200511020401
>
> Hi Ryan,
>
> It should work out of the box without having to call this method. I
> have created a standalone example that you can run in the sandbox that
> shows how this works. The example is attached to this email.
>
> Note that the element that has the id you used in XForms will be a
> span, not the input field - and this is how it is supposed to be. Have
> a look at the example, and if this is what you are doing and it does
> not work for you, there is somewhere an issue we need to figure out.
>
> Alex
>
> On 11/18/05, Ryan Puddephatt <[hidden email]> wrote:
> > Hi Erik & Alex,
> > I have found a little work around, by calling the
> > Xforms-dispatchEvent function after changing the value I have managed to
> > update the instance. Would this be the only way of doing it or could it be
> > included in OPS?
> >
> > Thanks
> >
> > Ryan Puddephatt
> > Web Developer
> > TFX Group
> > 1 Michaelson Square
> > Livingston
> > West Lothian
> > Scotand
> > EH54 7DP
> >
> > * [hidden email]
> > ( 01506 407 110
> > 7 01506 407 108
> >
> >
> > -----Original Message-----
> > From: Ryan Puddephatt [mailto:[hidden email]]
> > Sent: 17 November 2005 16:39
> > To: [hidden email]
> > Subject: RE: [ops-users] old instance data coming back to a page --
> version
> > 3.0.beta3.200511020401
> >
> > Thanks Erik, sorry was rather misleading at first! We do use the code as
> you
> > suggested to set the value, but it doesn't appear to be setting the
> > instance. Looking at Logging Events, OPS doesn't appear to notice the
> > change, could I run something in JavaScript to alert OPS to the change? Or
> > is it just a bug?
> >
> > Thanks
> >
> > Ryan Puddephatt
> > Web Developer
> > TFX Group
> > 1 Michaelson Square
> > Livingston
> > West Lothian
> > Scotand
> > EH54 7DP
> >
> > * [hidden email]
> > ( 01506 407 110
> > 7 01506 407 108
> >
> >
> > -----Original Message-----
> > From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
> > Sent: 17 November 2005 16:30
> > To: [hidden email]
> > Subject: Re: [ops-users] old instance data coming back to a page --
> version
> > 3.0.beta3.200511020401
> >
> > Ryan Puddephatt wrote:
> >
> > > I'm not trying to change the value of the id with JavaScript
> >
> > Sorry, I misunderstood because your sentence was a little misleading:
> >
> > "[...] the JavaScript [...] doesn't seem to be setting the ID of the
> > html:input control"
> >
> > > <span id="facilityID" class="xforms-control xforms-input"><span
> > > class="xforms-date-display"></span><input type="text" name="facilityID"
> > > value="" class="xforms-type-string"><span class="xforms-showcalendar
> > > xforms-type-string"></span></span>
> >
> > Yes, that's still a feature, not a bug ;-)
> >
> > > Alex said we would be able to set the id of the input control.
> >
> > I think what he said is that you would be able to set the value of the
> > control by doing something like (Alex, can you check this?):
> >
> > getElementById(id).value = myValue;
> >
> > This does not necessarily imply moving the id to the HTML <input>
> > element...
> >
> > > Also I have made a small work around for the time being, but the
> > > instance value of 'summaryUnderPointInFinancialTreeID' is not being
> > > changed even though the value of the control has changed via
> > > JavaScript
> > >
> > > So both bugs still appear to be there
> >
> > I think Alex should be able to confirm the following:
> >
> > 1) What Javascript syntax is supposed to work to update the value of
> > the control.
> >
> > 2) Whether setting the value in fact causes it to be set in the
> > instance - there may be a bug here.
> >
> > -Erik
> >
> >
> >
> >
> >
> >
> >
> >
> > --
> > 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
> > ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
> >
> >
> >
>
>
> --
> Blog (XML, Web apps, Open Source): http://www.orbeon.com/blog/
>
>
>
>
>
> --
> 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
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
>

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

Ryan Puddephatt

RE: old instance data coming back to a page -- version 3.0.beta3.200511020401

Alex,
I can see the <span> with the Id, and setting the value works, but
it only sets the value of the control it doesn't amend the instance value.
This is why I have had to call the dispatch event function. I just wanted to
clarify that this was the best way to go about it or if there was a better
way?

Thanks

Ryan Puddephatt
Web Developer
TFX Group
1 Michaelson Square
Livingston
West Lothian
Scotand
EH54 7DP

* [hidden email]
( 01506 407 110
7 01506 407 108

-----Original Message-----
From: [hidden email] [mailto:[hidden email]] On Behalf Of Alessandro
Vernet
Sent: 22 November 2005 19:52
To: [hidden email]
Subject: Re: [ops-users] old instance data coming back to a page -- version
3.0.beta3.200511020401

Ryan,

If you don't see the <span> around the <input> in the generated HTML,
you are most likely not running the latest version of OPS, or a
version that has not been completely updated.

We are now generating this span as the <xforms:input> can appear as
some text with a data picker or as a text field depending on the type
of the node bound to the <xforms:input>. We generate those two
possible forms and can switch at runtime using JavaScript as the type
of the node can change after the page is displayed.

Did you update the content of your resources/ops when getting the
latest "unstable build"?

Alex

On 11/19/05, Ryan Puddephatt <[hidden email]> wrote:
> Alex, I've run the page and it correctly works, but it doesn't appear to
> change the instance data. I've checked the logging events and nothing
shows

> up. Also when I look at the source for your page I see
>
> <input type="text" name="$portlet$p1.input" value="" id="input"
> class="xforms-control xforms-incremental">
>
> Whereas mine looked like
>
> <span id="input"> <input type="text" name="$portlet$p1.input" value=""
> name="input" class="xforms-control xforms-incremental"></span>
>
> I fixed this by searching for names to set the value and running the
> dispatchevent function to update the instance, we had previously been

using

> a similar JavaScript to you to get the element!
>
> Any Ideas
>
> Ryan Puddephatt
> Web Developer
> TFX Group
> 1 Michaelson Square
> Livingston
> West Lothian
> Scotand
> EH54 7DP
>
> * [hidden email]
> ( 01506 407 110
> 7 01506 407 108
>
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of Alessandro
> Vernet
> Sent: 19 November 2005 00:14
> To: [hidden email]
> Subject: Re: [ops-users] old instance data coming back to a page --

version

> 3.0.beta3.200511020401
>
> Hi Ryan,
>
> It should work out of the box without having to call this method. I
> have created a standalone example that you can run in the sandbox that
> shows how this works. The example is attached to this email.
>
> Note that the element that has the id you used in XForms will be a
> span, not the input field - and this is how it is supposed to be. Have
> a look at the example, and if this is what you are doing and it does
> not work for you, there is somewhere an issue we need to figure out.
>
> Alex
>
> On 11/18/05, Ryan Puddephatt <[hidden email]> wrote:
> > Hi Erik & Alex,
> > I have found a little work around, by calling the
> > Xforms-dispatchEvent function after changing the value I have managed to
> > update the instance. Would this be the only way of doing it or could it

> > included in OPS?
> >
> > Thanks
> >
> > Ryan Puddephatt
> > Web Developer
> > TFX Group
> > 1 Michaelson Square
> > Livingston
> > West Lothian
> > Scotand
> > EH54 7DP
> >
> > * [hidden email]
> > ( 01506 407 110
> > 7 01506 407 108
> >
> >
> > -----Original Message-----
> > From: Ryan Puddephatt [mailto:[hidden email]]
> > Sent: 17 November 2005 16:39
> > To: [hidden email]
> > Subject: RE: [ops-users] old instance data coming back to a page --
> version
> > 3.0.beta3.200511020401
> >
> > Thanks Erik, sorry was rather misleading at first! We do use the code as
> you
> > suggested to set the value, but it doesn't appear to be setting the
> > instance. Looking at Logging Events, OPS doesn't appear to notice the
> > change, could I run something in JavaScript to alert OPS to the change?

> > is it just a bug?
> >
> > Thanks
> >
> > Ryan Puddephatt
> > Web Developer
> > TFX Group
> > 1 Michaelson Square
> > Livingston
> > West Lothian
> > Scotand
> > EH54 7DP
> >
> > * [hidden email]
> > ( 01506 407 110
> > 7 01506 407 108
> >
> >
> > -----Original Message-----
> > From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
> > Sent: 17 November 2005 16:30
> > To: [hidden email]
> > Subject: Re: [ops-users] old instance data coming back to a page --
> version
> > 3.0.beta3.200511020401
> >
> > Ryan Puddephatt wrote:
> >
> > > I'm not trying to change the value of the id with JavaScript
> >
> > Sorry, I misunderstood because your sentence was a little misleading:
> >
> > "[...] the JavaScript [...] doesn't seem to be setting the ID of the
> > html:input control"
> >
> > > <span id="facilityID" class="xforms-control xforms-input"><span
> > > class="xforms-date-display"></span><input type="text"

name="facilityID"

> > > value="" class="xforms-type-string"><span class="xforms-showcalendar
> > > xforms-type-string"></span></span>
> >
> > Yes, that's still a feature, not a bug ;-)
> >
> > > Alex said we would be able to set the id of the input control.
> >
> > I think what he said is that you would be able to set the value of the
> > control by doing something like (Alex, can you check this?):
> >
> > getElementById(id).value = myValue;
> >
> > This does not necessarily imply moving the id to the HTML <input>
> > element...
> >
> > > Also I have made a small work around for the time being, but the
> > > instance value of 'summaryUnderPointInFinancialTreeID' is not being
> > > changed even though the value of the control has changed via
> > > JavaScript
> > >
> > > So both bugs still appear to be there
> >
> > I think Alex should be able to confirm the following:
> >
> > 1) What Javascript syntax is supposed to work to update the value of
> > the control.
> >
> > 2) Whether setting the value in fact causes it to be set in the
> > instance - there may be a bug here.
> >
> > -Erik
> >
> >
> >
> >
> >
> >
> >
> >
> > --
> > 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
> > ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
> >
> >
> >
>
>
> --
> Blog (XML, Web apps, Open Source): http://www.orbeon.com/blog/
>
>
>
>
>
> --
> 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
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
>

Alessandro Vernet

Re: old instance data coming back to a page -- version 3.0.beta3.200511020401

Administrator

Ryan,

The value should be set and the instance modified automatically. So it
seems there is a problem somewhere. Can you:

1) Have a look at the attached file. It runs in the XForms sandbox.
See if what you are doing is similar. From what I understand, this is
exactly what you are doing, and at least it works for me in this use
case.
2) If that doesn't help, can you create a stand-alone XForms file that
I can run the XForms sandbox and that shows the problem?

Alex

On 11/23/05, Ryan Puddephatt <[hidden email]> wrote:

> Alex,
> I can see the <span> with the Id, and setting the value works, but
> it only sets the value of the control it doesn't amend the instance value.
> This is why I have had to call the dispatch event function. I just wanted to
> clarify that this was the best way to go about it or if there was a better
> way?
>
> Thanks
>
> Ryan Puddephatt
> Web Developer
> TFX Group
> 1 Michaelson Square
> Livingston
> West Lothian
> Scotand
> EH54 7DP
>
> * [hidden email]
> ( 01506 407 110
> 7 01506 407 108
>
>
> -----Original Message-----
> From: [hidden email] [mailto:[hidden email]] On Behalf Of Alessandro
> Vernet
> Sent: 22 November 2005 19:52
> To: [hidden email]
> Subject: Re: [ops-users] old instance data coming back to a page -- version
> 3.0.beta3.200511020401
>
> Ryan,
>
> If you don't see the <span> around the <input> in the generated HTML,
> you are most likely not running the latest version of OPS, or a
> version that has not been completely updated.
>
> We are now generating this span as the <xforms:input> can appear as
> some text with a data picker or as a text field depending on the type
> of the node bound to the <xforms:input>. We generate those two
> possible forms and can switch at runtime using JavaScript as the type
> of the node can change after the page is displayed.
>
> Did you update the content of your resources/ops when getting the
> latest "unstable build"?
>
> Alex
>
> On 11/19/05, Ryan Puddephatt <[hidden email]> wrote:
> > Alex, I've run the page and it correctly works, but it doesn't appear to
> > change the instance data. I've checked the logging events and nothing
> shows
> > up. Also when I look at the source for your page I see
> >
> > <input type="text" name="$portlet$p1.input" value="" id="input"
> > class="xforms-control xforms-incremental">
> >
> > Whereas mine looked like
> >
> > <span id="input"> <input type="text" name="$portlet$p1.input" value=""
> > name="input" class="xforms-control xforms-incremental"></span>
> >
> > I fixed this by searching for names to set the value and running the
> > dispatchevent function to update the instance, we had previously been
> using
> > a similar JavaScript to you to get the element!
> >
> > Any Ideas
> >
> > Ryan Puddephatt
> > Web Developer
> > TFX Group
> > 1 Michaelson Square
> > Livingston
> > West Lothian
> > Scotand
> > EH54 7DP
> >
> > * [hidden email]
> > ( 01506 407 110
> > 7 01506 407 108
> >
> >
> > -----Original Message-----
> > From: [hidden email] [mailto:[hidden email]] On Behalf Of Alessandro
> > Vernet
> > Sent: 19 November 2005 00:14
> > To: [hidden email]
> > Subject: Re: [ops-users] old instance data coming back to a page --
> version
> > 3.0.beta3.200511020401
> >
> > Hi Ryan,
> >
> > It should work out of the box without having to call this method. I
> > have created a standalone example that you can run in the sandbox that
> > shows how this works. The example is attached to this email.
> >
> > Note that the element that has the id you used in XForms will be a
> > span, not the input field - and this is how it is supposed to be. Have
> > a look at the example, and if this is what you are doing and it does
> > not work for you, there is somewhere an issue we need to figure out.
> >
> > Alex
> >
> > On 11/18/05, Ryan Puddephatt <[hidden email]> wrote:
> > > Hi Erik & Alex,
> > > I have found a little work around, by calling the
> > > Xforms-dispatchEvent function after changing the value I have managed to
> > > update the instance. Would this be the only way of doing it or could it
> be
> > > included in OPS?
> > >
> > > Thanks
> > >
> > > Ryan Puddephatt
> > > Web Developer
> > > TFX Group
> > > 1 Michaelson Square
> > > Livingston
> > > West Lothian
> > > Scotand
> > > EH54 7DP
> > >
> > > * [hidden email]
> > > ( 01506 407 110
> > > 7 01506 407 108
> > >
> > >
> > > -----Original Message-----
> > > From: Ryan Puddephatt [mailto:[hidden email]]
> > > Sent: 17 November 2005 16:39
> > > To: [hidden email]
> > > Subject: RE: [ops-users] old instance data coming back to a page --
> > version
> > > 3.0.beta3.200511020401
> > >
> > > Thanks Erik, sorry was rather misleading at first! We do use the code as
> > you
> > > suggested to set the value, but it doesn't appear to be setting the
> > > instance. Looking at Logging Events, OPS doesn't appear to notice the
> > > change, could I run something in JavaScript to alert OPS to the change?
> Or
> > > is it just a bug?
> > >
> > > Thanks
> > >
> > > Ryan Puddephatt
> > > Web Developer
> > > TFX Group
> > > 1 Michaelson Square
> > > Livingston
> > > West Lothian
> > > Scotand
> > > EH54 7DP
> > >
> > > * [hidden email]
> > > ( 01506 407 110
> > > 7 01506 407 108
> > >
> > >
> > > -----Original Message-----
> > > From: Erik Bruchez [mailto:[hidden email]] On Behalf Of Erik Bruchez
> > > Sent: 17 November 2005 16:30
> > > To: [hidden email]
> > > Subject: Re: [ops-users] old instance data coming back to a page --
> > version
> > > 3.0.beta3.200511020401
> > >
> > > Ryan Puddephatt wrote:
> > >
> > > > I'm not trying to change the value of the id with JavaScript
> > >
> > > Sorry, I misunderstood because your sentence was a little misleading:
> > >
> > > "[...] the JavaScript [...] doesn't seem to be setting the ID of the
> > > html:input control"
> > >
> > > > <span id="facilityID" class="xforms-control xforms-input"><span
> > > > class="xforms-date-display"></span><input type="text"
> name="facilityID"
> > > > value="" class="xforms-type-string"><span class="xforms-showcalendar
> > > > xforms-type-string"></span></span>
> > >
> > > Yes, that's still a feature, not a bug ;-)
> > >
> > > > Alex said we would be able to set the id of the input control.
> > >
> > > I think what he said is that you would be able to set the value of the
> > > control by doing something like (Alex, can you check this?):
> > >
> > > getElementById(id).value = myValue;
> > >
> > > This does not necessarily imply moving the id to the HTML <input>
> > > element...
> > >
> > > > Also I have made a small work around for the time being, but the
> > > > instance value of 'summaryUnderPointInFinancialTreeID' is not being
> > > > changed even though the value of the control has changed via
> > > > JavaScript
> > > >
> > > > So both bugs still appear to be there
> > >
> > > I think Alex should be able to confirm the following:
> > >
> > > 1) What Javascript syntax is supposed to work to update the value of
> > > the control.
> > >
> > > 2) Whether setting the value in fact causes it to be set in the
> > > instance - there may be a bug here.
> > >
> > > -Erik
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > --
> > > 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
> > > ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
> > >
> > >
> > >
> >
> >
> > --
> > Blog (XML, Web apps, Open Source): http://www.orbeon.com/blog/
> >
> >
> >
> >
> >
> > --
> > 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
> > ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
> >
> >
> >
>
>
> --
> Blog (XML, Web apps, Open Source): http://www.orbeon.com/blog/
>
>
>
>
>
>
> --
> 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
> ObjectWeb mailing lists service home page: http://www.objectweb.org/wws
>
>
>

input-javascript.xhtml (1K) Download Attachment

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