If the js runtime or context or global window cannot be created, it prints a message to that effect, leaves jss null, and returns. This is the first non-exit error leg in our js world. Without the context, javascript is disabled, but edbrowse continues to run. You can test this easily. Edit Chris memory hogging array program and another html file. Browse the first and get the memory full error. Switch to buffer 2 and browse the second, but there isn't enough memory to set up the window, so the context is not created, jss is null, and any javascript features in that second file, like onclick push buttons, won't work. This is I think the start of where we want to go. Other error legs will print a message, distroy context, set jss to null, and return.
Karl Dahlke _______________________________________________ Edbrowse-dev mailing list [email protected] http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
