On Tuesday, December 17, 2013 5:02:00 AM UTC-5, mike ryder wrote: > > You can do it in code for VT100 type emulation - see > http://pwchest.no-ip.biz/qmweb/base/wiki?id=jslibs:vtcode for the escape > codes > > If you send HEX(1B2830) you will switch into a graphics mode and then send > HEX(1B2842) and you switch back to US ASCII output > > <codesnip> > GO = OCONV('1B2830','MX0C') > GX = OCONV('IB2842','MX0C') > TOPLEFT = OCONV('6C','MX0C') > PRINT GO:TOPLEFT:GX > </codesnip> > > The code snip will print the top left corner of a box. > > Mike > > > If I understand correclty, you're pointing out the escape codes. Is that right?
The run-time solution I mentioned seems preferable to hard coding the escape codes. At run time, the codes can be read from the system instead of assuming what that they will always be the same. But the dilemma is whether or not to use jbase screen codes that look like @(-##). The screen codes are functionality built into and specific to jbase but unfortunately that functionality is dictated at compile time. The runtime solution appears to be more robust in the face of possible future changes. I am interested in if people think that is an accurate assessment. -- -- 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.
