Part 1: I need help I am not sure which forum this belongs in...
I had the opportunity to use jhs on a reasonably fast machine. Not super fast, maybe, but 6 cores, each 3.5GHz, 12gb ram, terrabyte hard disk... Anyways, on this machine, jhs would often take 5 seconds to respond, after I hit enter. The machine was practically unloaded, and some responses were quick, but many took five seconds. This was using IE for the web browser (other browsers were not an option). This was a current jhs (updated to current versions of all packages a few days ago). Has anyone seen anything like this before? Does anyone know what I might do to isolate the issue? ---------------- Part 2: notes related to ui design Also, I should note that the jhs browser implementation does not provide very good feedback about whether it's waiting or not, in this situation. For example, when using r to save and run a script: 1. It's not clear when the focus is proper so that r can be sent, and 2. After the first save and run instance, it's not clear whether the message being displayed is current or historic and it's not clear when it's done. I can tell if the browser is waiting by looking at the upper right hand corner of the browser, but this is a very subtle effect. I can sometimes get a "please wait" message by repeating my attempts. -- Raul ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
