It was probably getting previously bit by compile-time JBCEMULATE settings that made me wary of using @(-##) screen codes tied to a specific emulation mode. The cursor-right code differs between ROS and jbase emulations. Just this week I accidentally triggered over 12000 print jobs by pressing the right arrow key. It should have just caused a single screen dump but somehow the terminal emulator or win7 got stuck and generated that many jobs before I managed to kill it.
We will need to recompile much of our jbase system to switch emulation modes and the thought was to avoid possibly needing to do that again in the future. Granted, we'll probably never change emulation modes again. It isn't that the escape code for vt100 alternate character set toggling would change. But rather that the @(-##) codes might be a less future proof way of accessing functionality that isn't specific to jbase. With further thought spurred by responses here and from coworkers, it seems that it might not matter much. Though now that I have a non-jbase-dependent run-time solution for accessing terminal functionality, that seems preferable. -- -- IMPORTANT: T24/Globus posts are no longer accepted on this forum. To post, send email to [email protected] To unsubscribe, send email to [email protected] For more options, visit this group at http://groups.google.com/group/jBASE?hl=en --- You received this message because you are subscribed to the Google Groups "jBASE" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
