Hi,

Seems like a small issue but - in the double list box when we deselect some values from the right side back on to the left side - values are being added at the bottom of the left side select box instead of the original slot. I think the JS is adding the values at the end incrementally. Users are confused - when the list is long they have to scroll down and search for it if they want to add it back again.
May be the JS can cache/remember the positions of the list values and add them back to the original positions.
Now I am trying to repopulate the listbox onclick of the deselect button to resort them in original order.


thanks
Sashanka

Sashanka, I've used jQuery (because it makes it easier) to copy the left-side dropdown box to a hidden dropdown box in onInitialUpdate(), then I use the hidden dropdown box to repopulate the left-side dropdown box.

Another technique you could try is to use JS (or jQuery) to sort the values upon some event...

It would be nice if this happened automatically.

quote:

Originally posted by David Glick:
Wep,

We believe by showing the population at design time, the designer will see a problem occur immediately. They will not have to run the page to see it. We are also thinking of popup messages when something is done that affects something else, for example, the designer modifies the default population request, so now any chained controls need to have their population inspected to make sure it is still valid.

IMO, the problem isn't so much that people don't notice that control chains break, but that that happens in the first place. Having to find out by testing doesn't help of course, so doing something about that is probably still a step forward, but it only fixes symptoms, not cause.

I also think that people aren't going to appreciate popup messages. IMHO it would be better to have visual cues in the design window that certain connections aren't working, for example by colouring a chain-link red and showing an informative(!) tooltip when hovering the mouse over it (For example "Field CAR doesn't exist in source control" or some such).

quote:

Originally posted by David Glick:
For tab index, we are going to make the automatic creation optional. It will be on by default since we need to maintain current behavior, but it can be turned off.

Being able to turn it off by default is a start.

It'd be much more helpful, I think, to have a visual cue what Tab index each control has (for example through a little coloured box in a corner of the control with the tab index number). Being able to drag the numbers around to change the tab ordering of the controls on screen would make things even better. Of course people will want the ability to hide/show these tab index number cues, but I'd show them by default.

There is a visual cue when you hit the tab order button on the toolbar. It should a number on each object which is the tab order.