--------------- FIDO MESSAGE AREA==> TOPIC: 152 QEDIT Ref: F1F00000 Date: 01/09/98 From: ROSS_BOYD@TNT.COM.AU Time: 07:42am \/To: ALL (Read 0 times) Subj: Question: Limiting keys in a Read() From: Ross_Boyd@tnt.com.au Hi all, Can someone point me towards a way to limit the available keys in a Read()? I want to force input to UpperCase - _as_ it is _typed_. Also, a way to limit the user to just a set of characters would be helpful. Thanks in advance, Ross --- * Origin: apana<<<<<<>>>>>>fidonet [sawasdi.apana.org.au] (3:800/846.13) --------------- FIDO MESSAGE AREA==> TOPIC: 152 QEDIT Ref: F1F00001 Date: 01/09/98 From: ROSS_BOYD@TNT.COM.AU Time: 07:46am \/To: ALL (Read 0 times) Subj: TSE/Pro 2.8b Tip: How to get a list of d07:46:3001/09/98 From: Ross_Boyd@tnt.com.au Hi all, Maybe someone is interested in this. Last night I was experimenting with a function to return a list of valid drives and came across this little gem. There is a function GetNextConnection() which will give you a list of valid drives like this: -------------------------------------------------------------------------- string proc GetDriveString() string drive[20] = "" string drivestr[80] = "" while GetNextConnection(drive) drivestr = drivestr + drive + " " endwhile return(drivestr) end proc Main() Warn("DriveList=",GetDriveString()) end --------------------------------------------------------------------------- integer proc GetNextConnection(drive) sequentially sets the passed string variable to the drive letter including colon. It returns false/0 when there are no more drives (at which point it begins again at the first valid drive). Also, it skips the logical floppy B: drive (if you only have one floppy A: drive) See example above. It's _much_ faster than testing the return of LogDrive('a' to 'z') in a loop. I think its limited to TSE 2.8b although I haven't actually checked. Hope this is of use to someone. Cheers, Ross --- * Origin: apana<<<<<<>>>>>>fidonet [sawasdi.apana.org.au] (3:800/846.13) --------------- FIDO MESSAGE AREA==> TOPIC: 152 QEDIT Ref: F1F00002 Date: 01/09/98 From: MICHAEL LANG Time: 03:13pm \/To: ALL (Read 0 times) Subj: GUI version of TSE? From: abraxas@hamburg.snafu.de (Michael Lang) Sammy, I hope, that you'll release the 32bit DOS version of TSE/Pro, of which you talked here a couple of weeks ago. Must be a super program! <*** ml ***> --- * Origin: apana<<<<<<>>>>>>fidonet [sawasdi.apana.org.au] (3:800/846.13) --------------- FIDO MESSAGE AREA==> TOPIC: 152 QEDIT Ref: F1F00003 Date: 01/09/98 From: HS Time: 05:00pm \/To: ALL (Read 0 times) Subj: GUI version of TSE? From: HS Michael, Hmmm. I really don't understand this. It was my dealer who installed TSE3= 2 Demoversion and he REALLY knows Jaws for Windows. I also use it in Window= s AND DOS boxes withaut any problem. Well, I will waite for the GUI version= =2E I noticed that editing with any wordprocessor or Win Editor from Win95 is= w=F6rlds slower than in DOS with a braille display. Regards Hanspeter --- * Origin: apana<<<<<<>>>>>>fidonet [sawasdi.apana.org.au] (3:800/846.13) --------------- FIDO MESSAGE AREA==> TOPIC: 152 QEDIT Ref: F1F00004 Date: 01/10/98 From: "CHRIS ANTOS (EXCHANGE)" Time: 03:48am \/To: ALL (Read 0 times) Subj: Re: GUI version of TSE? From: "Chris Antos (Exchange)" fyi, console mode apps are not "just like DOS apps except they use Windows resources". they are hugely different on a technical level, *especially* when it comes to screen output. the screen output mechanism is nothing like DOS programs. however, the output ends up *looking* the same as a DOS box, but that's about where the similarity ends. however, a screen reader can use several Win32 commands to access the screen output very easily, so yes it should be a piece of cake for a screen reader to work. not sure why screen readers are slower on GUI and console apps than on DOS apps, but it doesn't surprise me given what the screen reader has to do. -----Original Message----- From: abraxas@hamburg.snafu.de [mailto:abraxas@hamburg.snafu.de] Sent: Thursday, January 08, 1998 9:43 PM To: tsepro@semware.com Subject: GUI version of TSE? Hanspeter, I also use a Braille display and I CAN use Tse/32. I haven't baught it, since it's slower than TSE/pro 2.5 on my PC with Windows 95, but I had no problems using the demo version. You should be able to use TSE/32 with a Windows screen reader, that supports DOS boxes. Or you could use it with a DOS screen reader in a Windows 95 DOS box. Console mode programs like TSE/32 behave like DOS programs, except that they use Windows resources, so they have to be run under Windows. But their screen output style is identical to DOS programs. <*** ml ***> You wrote: > Amont others i, too, wait for it. I tried out TSE32 (V.2.8?) but it did n= > ot > work with my braille display nor did it with speech. My dealer says the > screen remains black and that this is because the screen reader software > expects graphical input and the one of the console version is not. Well, = > I > don't know. > > Hope your gui version comes soon. > > Hanspeter --- * Origin: apana<<<<<<>>>>>>fidonet [sawasdi.apana.org.au] (3:800/846.13) --------------- FIDO MESSAGE AREA==> TOPIC: 152 QEDIT Ref: F1F00005 Date: 01/09/98 From: ROSS_BOYD@TNT.COM.AU Time: 08:12am \/To: ALL (Read 0 times) Subj: Re: Question: Limiting keys in a Read() From: Ross_Boyd@tnt.com.au Hi, This is weird. Now I'm answering my own Email :) I found a way of doing this. The solution might be instructive for some. The trick is to Hook() into the _AFTER_GETKEY_ event and update the key using Set(key,whatever). Here's an example of forcing capitals and disallowing numerics: // Hooked to _AFTER_GETKEY_ event proc UpperCaseFilteredRead() integer ikey = Query(key) if ikey in .. // Uppercase the key Set(key, ikey^32) elseif ikey in <0>..<9> // I want to ignore the above numeric keys // This forces the key to a non-typeable key Set(key, ) endif end proc Main() string inputstr[20] = "" Hook(_AFTER_GETKEY_,UpperCaseFilteredRead) if Read(inputstr) Message("You typed:",inputstr) endif Unhook(UpperCaseFilteredRead) end Question: Is there a better way than forcing invalid keys to ?? Any feedback appreciated, Ross Boyd ---------------------------- From: Ross.Boyd To: tsepro Subject: Question: Limiting keys in a Read() Date: Thursday, 8 January 1998 14:12 Hi all, Can someone point me towards a way to limit the available keys in a Read()? I want to force input to UpperCase - _as_ it is _typed_. Also, a way to limit the user to just a set of characters would be helpful. Thanks in advance, Ross --- * Origin: apana<<<<<<>>>>>>fidonet [sawasdi.apana.org.au] (3:800/846.13) --------------- FIDO MESSAGE AREA==> TOPIC: 152 QEDIT Ref: F1F00006 Date: 01/09/98 From: "SAMMY MITCHELL" Time: 08:58am \/To: ALL (Read 0 times) Subj: Re: Question: Limiting keys in a Read() From: "Sammy Mitchell" >This is weird. Now I'm answering my own Email :) That is strange . >Question: Is there a better way than forcing invalid keys to ?? Setting it to -1 is probably the best. For instance, that is what we do in the CUAMark macro, so you can be pretty sure this will also work in the future! Sammy --- * Origin: apana<<<<<<>>>>>>fidonet [sawasdi.apana.org.au] (3:800/846.13)