____ ___ ____ ___ | \ / _] / | | \ | D ) / [_ | o | | \ | / | _] | | | D | | \ | [_ | _ | | | | . | | | | | | | | l__|\_| l_____| l__|__| l_____| THE S/´C READ ROUTINES 1.0f INCLUDED IN THE ZIP ARCHIVE: EXAMPLE.PPS AN EXAMPLE SOURCE CODE! FILE_ID.DIZ FILE DESCRIPTION READ.DOC YOU ARE READING THIS READ.LIB THE SOURCE CODE ITSELF SAC.NFO SUPERIOR ART CREATIONS INFO FILE SUPPORT.ANS SHOGUNAT BBS ADDY 1.) (ì) What's it all about (ì) - The read routine was made for PPL coders, who want to get inside the INSTR() / INPUTXXX Procedurse, my read routine replaces the procedure from CDC, and has similar features - Full comfort of DEL, BACKSPACE, L/R CURSOR, HOME, END - Insert modus - Wordwrapping - Color support - compiles with pplc 3.0+ - You can get inside the routine to use your own keys... - Maybe you want to have ALT/CTRL + KEY for saving Or Ctrl-C for aborting, or whatever, you can use my sources for it. 2.) (ì) How to use (ì) - There are two ways a) In your program header include: BEGIN ; (...) *$INCLUDE:READ.LIB ; (...) b) Copy the function declaration and the declaration itself to your pps, but to keep your own creation "easy-to-view" it would be easier to use a) - CHECK OUT THE EXAMPLE.PPS !!! It's easier to "learn-by-doing" than to waste time trying to understand all of this documentation! - Syntax: VARXX=READ(X-COORDINATE,Y-COORDINATE,LENGTH, WORDWRAP) - X-Cord VALID: 0 to 79 This is the x position of the cursor for input, you can of course put GETX() here for current Cursor Position - Y-Cord VALID: 0 to 23 (PPL Doesn support 50 Line mode!) This is the y position of the cursor for input, you can of course put GETY() here for current Cursor Position. - Length VALID: 1 to 79 In fact the size is not limited but you should keep it to screen width! - Wordwrap VALID: 0 and 1 Put 1 to use word wraping and 0 for no wordwrapping - Example: BEGIN *$INCLUDE:READ.LIB STRING NAME NAME=READ(GETX(),GETY(),24,0) PRINT NAME NEWLINE END 3.) (ì) Some words about coding editors (ì) - Now, that you have expierienced, how easy it is to code reading routines, you surely plan to code a small message editor or something! The most importent thing to remember when coding read/editing routines, NEVER try to save the string, each time the user hits a key, just COPY (SAVE) the Screen to disk (or a variable) using SCRTEXT!!! Any other thing is HORRIBLE difficult! I think that all these oneliners are badly coded because of that, remember the last paramter of SCRTEXT has to be TRUE (=1) if you want to save the colors! remember that each color code takes 4 chars so use bigstring with colorful things! Password routines are the only exception, where SCRTEXT won't work (caus you will always save the dots), but who needs wordwrapping, delete, and insert modus in such routines either ? - If lots of people write me a mail than i will releas an EDIT.LIB, so that your lame "C" replacement will finally be worth more than a dime! 4.) (ì) Specifications for advanced Coders (ì) - Let 's talk about TIMING problems, the INKEY() function uses more processor capacity than tinkey(0), so when you know, that someone uses a multitasking system it's better to use the timed inkey TINKEY(0), however this is a future of pcboard 15.22 and future versions so some ppl can't use it ... A possability to test for multitasker is just this: SELECT CASE ( OS() ) CASE 0: Println "Whatta fuck" CASE 1: WHiLE (KEYREAD="") KEYREAD=INKEY() CASE 2: WHiLE (KEYREAD="") KEYREAD=TINKEY(0) END SELECT Be sure to use TINKEY(0) instead of inkey() when somebody uses the 32bit pcboard version, as well as SOUNDDELAY(FREQ, LEN) instead of SOUND, because they need the correct timing, and OS/2 has totally different timing than DOS! - If you want to change the colors or optimize the colors see the sample code inside the read.lib 5.) (ì) Last Words (ì) - If you find Any bugs please CONTACT ME and report the bugs I am reachable in many boards in germany! Or enter a message to any sac or xadi member, they know how to contact me! - You can change the main code as you want for your use BUT: - You may not release changed READ Sources - You have to Credit SAC and the Coder CyZ in the ppe or doc/nfo if you use our read routines - If you want to contact me for PPE Request or chat or whatever look inside the SAC info for my board number! DON'T try to contact me for anti-decompilation routines, we won't give them away! ..../(____)\ /(____)\... signing of Code finished on øø|:. ___/ \___ .:|øø CyZ / SaC 4th February '96 |:. / )\_ _/( / _/ contact me on Thanks to all who .|:. \__)\_ \/ _/ _/_)\. any big scene beta tested this! .:::\______/.\ _/<______/::. board! / / S/´C \| ø