at 10:53 am EDT on (Wednesday) 19 November 2003 Miguel said: > >> 1. This "button" is never seen by an end-user > >> > > that is correct, although I make it visible for testing purposes now > > and again. > > How do you make it visible/invisible? > it is on an html layer; I just change the visibility property of the layer.
> Would it benefit from any other 'special' behavior to facilitate > debugging? > it's not debugging, but... at the moment, I rewrite the html for the button every time I want to send a new script to JMol. it would be awfully nice to be able to simply change the script value of the existing button via javascript and having the button press itself again - something like an onChange handler. > For example, should it behave like a regular button sometimes ... to > facilitate debugging? > would it be different from changing the type from "immediate" to "button"? regards, :tim -- timothy driscoll molvisions - molecular graphics & visualization <http://www.molvisions.com/> usa:north carolina:wake forest ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ Jmol-users mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jmol-users
