I notice you are using a standard action-popup, which has the follow caveat:
The popup will dutifully report back the fwValue, even if that value is no longer a possibility in the items list. For instance if the items[] list included a value of ‘sample’ and that was explicitly chosen, then the fwVaue would be ‘sample’. However, if the items[] list changes, by the item that once held that action is deleted, for instance, the value ‘sample’ would not appear in the list, but the fwValue would still report ‘sample’.
The kicker, if I remember correctly, is that the action-popup would then list back to the user the first value, even though it was not explicitly selected. So what I end up doing for this situations to avoid confusion for the customer is to add an ‘instructional’ line like: ‘Choose Item:’ (blank probably would work).
IMPORTANT: So you would have to interrogate the fwValue, then compare to the fwMenuItems to make sure that the value is still valid. ((this ‘glitch’ is actually a blessing because if/when items[fwValue] becomes available again, then the action parameter correctly picks up on the value again.))
The action itemref correctly returns null if the item becomes unavailable from the item list. And, better yet, tracks changes to the item name, so the connection is not broken if the item value changes. I have not investigated an initial value, or if it could be ‘hacked’ the same way as the action-popup by setting the value.
I do believe with action-itemref you lose the possibility of an associative list that could be used to display a ‘pretty’ list to the user. It has been a while since I have played with dynamic popups.
So, can all this run inside of fwInterface, then? It sounds amazing, certainly much simpler and less fragile than the many many steps I had to take to get mine to work.
PS: as you might guess, this message was supposed to be sent under your ‘dynamic list’ thread. Just in case the website code has regressed a bit, this was sent via the web interface, and I did again have multiple tabs open.
I noticed that, but I’m not sure what’s going on there. I haven’t
changed anything since I (thought I) fixed it.
Walter
On Nov 9, 2007, at 9:11 AM, Weaver wrote:
PS: as you might guess, this message was supposed to be sent under
your ‘dynamic list’ thread. Just in case the website code has
regressed a bit, this was sent via the web interface, and I did
again have multiple tabs open.
Sometime around 9/11/07 (at 09:11 -0500) Weaver said:
PS: as you might guess, this message was supposed to be sent under
your ‘dynamic list’ thread. Just in case the website code has
regressed a bit, this was sent via the web interface, and I did
again have multiple tabs open.
Something rather screwy happened too, at least in the version I see.
The subject text has been encoded so I see the ‘less than’ and
‘greater than’ codes in the raw.
Weaver, this is excellent! I noticed that my previous code would break if you renamed the target elements after setting up the tabs. Using your approach, they are now able to pick up on those changes immediately.
I ended up doing the following to set the initial value, I am sure it could be optimized, but it works for now.
function fwInterface(){
if(fwParameters['targets'].fwValue == null){
var carousel = fwPage.fwFindAction(2,'Carousel');
if(carousel) {
carousel = carousel.fwItem;
var targets = new Array();
var theEnd = false;
for (i in carousel.fwItems){
if(theEnd == false){
fwParameters['targets'].fwValue = carousel.fwItems[i];
theEnd = true;
}
}
}
}
}
This is an old subject, made in the previous system, and since the
old system stored encoded text, it is getting double-encoded on
output. Not much I can do about it. It doesn’t happen going forward,
only if you revive an old subject that had encoded text.
Walter
On Nov 9, 2007, at 8:10 PM, Keith Martin wrote:
Sometime around 9/11/07 (at 09:11 -0500) Weaver said:
PS: as you might guess, this message was supposed to be sent under
your ‘dynamic list’ thread. Just in case the website code has
regressed a bit, this was sent via the web interface, and I did
again have multiple tabs open.
Something rather screwy happened too, at least in the version I see.
The subject text has been encoded so I see the ‘less than’ and
‘greater than’ codes in the raw.