> Alternate behaviors could be:
>
> 1) replace the old alert window by the new one (I don't
> like that, because in some cases an important message in
> the first alert window may disapear before the user could read
> it and acknowledge).
>
> 2) stack-up alert windows (like Netscape does)
>
> 3) fl_show_alert() would block if the previous alert window
> was not closed by the user.
>
> (3) is better than (1), but I would prefer (2).
I agree that the current alert method is annoying - perhaps there should be two
different goodies (or add a flag to determine behaviour).
fl_show_alert - simply an alert box for warnings - doesn't block and stacks up
like those alert windows in Netscape.
fl_show_error - used for more important, actual error messages (not warnings)
and blocks until the user clicks OK. This, I reckon, would be highly useful for
"proper" errors which are caught by the program.
What do you think ?
TicH
------------------------------------------------------------------------
| Name - Richard Kent |
| EMail - kent@hydra.dra.hmg.gb |
| Plan - All work and no play.....hi ho, hi ho |
------------------------------------------------------------------------
_________________________________________________
To unsubscribe, send the message "unsubscribe" to
xforms-request@bob.usuf2.usuhs.mil or see
http://bob.usuf2.usuhs.mil/mailserv/xforms.html
Xforms Home Page: http://bragg.phys.uwm.edu/xforms
List Archive: http://bob.usuf2.usuhs.mil/mailserv/list-archives/xforms-archive/