Hi Alan,
You said:
> #DO TEXT INPUT WITH ENTRY ON NEXT LINE!
> def text_Input(prompt):
> print prompt
> return (raw_input(">> "))
Just use:
raw_input(prompt + "\n>> " )
Yes, that is OK if you are sighted, for the screen reader program does
not say the message in the prompt unless there is some kind of a change in
the screen.
I have to place it there for only a sightless programmer. Maybe once in
a while it would say it, but that is if the key stroke is fast and the kill
speech is quick. Like the purge command inside the example, when that is set
for all key strokes in a screen reader, it can erase any saying of text
displayed fast onto the screen, just a timing issue between keyboard and
screen reader capture.
So, my example is just accommodating that.
The other examples are true, I sent it without making the needed
changes. Probably too many try statements only because I wrote an input for
my Trek program that entered values of a given type and kind of left it
there if the wrong type is entered. Which brings up the other dictionary
list of keys. Just left it there when sending the example to fast. Just like
the last method which uses pygame, but it is never called and would fail
since I did not import pygame.
So, sending an outdated example is not good, but does lead to showing
the correct sample in a tutorial when you point out errors or sloppy work.
Thanks, Bruce
_______________________________________________
Tutor maillist - Tutor@python.org
http://mail.python.org/mailman/listinfo/tutor
