Re: Problem with WHEN-LIST-CHANGED trigger behavior

In article <361E6364.163B_at_nospam.us.oracle.com>,   czetie_at_nospam.us.oracle.com wrote:
> beansboy_at_my-dejanews.com wrote:
> >
> > You're correct - it only will fire when it changes.
> >
> > This is one idea (maybe not the best one) -- in your list, have a 'not
> > selected' list element. In your when_list_changed code, at the end have it
> > manually assign the 'not selected' value to the list. That means that when
> > the user would like to select something, he/she will have to change the
> > value.
> >
> > This might be a little confusing to the user - they select something, and
the
> > list zips back to 'not selected', but whatever they asked for is done...
> >
>
> Maybe the reason that it's confusing is that choosing from a poplist
> is an unusual way for a user to specify an action? Suggests to me
> that maybe this aspect of the UI should be re-examined?
>

It all depends on if it's very clear that it's an 'action' button. Making a list item into an 'action' type item is kind of neat because it doesn't take up much space (ie on a toolbar you can have one item kick off all kinds of things). If it's clear to the user that that is what it does, it's problably just fine.

-jay

[Quoted] -----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Sat Oct 10 1998 - 02:00:17 CEST