Re: A History of Variables
- From: Andreas Stefik <stefika@xxxxxxxxx>
- To: programmingblind@xxxxxxxxxxxxx
- Date: Tue, 13 Oct 2009 16:04:34 -0500
Do you think it would be better to have the history of variables available
from within the watch window or from a separate window which you can get to
easily? (Maybe by pressing enter on a row in the watch window)
Stefik
On Tue, Oct 13, 2009 at 3:19 PM, Alex Hall <mehgcap@xxxxxxxxx> wrote:
> Maybe a keystroke like ctrl-equals, since the equals key is used to
> assign values to variables. Then you can type all or part of the var name in
> question into an edit box that comes up. As you type, a list of all
> variables beside the box sorts itself so that the one it thinks you want is
> at the top, followed by the next most likely and so on. You can therefore
> tab to the list and select a variable, or just type the entire name. After
> that comes a list of all values the var has had, from most recent to least
> (though that order could maybe change). One more tab to the cancel button,
> then tab again to get back to typing a new variable name.
>
>
> Have a great day,
> Alex
> New email address: mehgcap@xxxxxxxxx
>
> ----- Original Message -----
> *From:* Andreas Stefik <stefika@xxxxxxxxx>
> *To:* programmingblind@xxxxxxxxxxxxx
> *Sent:* Tuesday, October 13, 2009 4:04 PM
> *Subject:* A History of Variables
>
> Hello folks,
>
> My student and I are working on part of our auditory debugger (in Sodbeans)
> related to its ability to "go backwards." Essentially, our debugger allows
> you to see (or hear) any value of any variable that has previously been set
> in the program. We have a number of ideas about how we can structure the
> audio portion of the debugger, but we're curious, if such a feature were
> available to you, how would you like it to work. As such, we pose the
> following question:
>
> Suppose your debugger could execute in reverse and return, in audio, the
> value of any variable that has ever been set in your program. Using only the
> keyboard, how would you like to access such information?
>
> While much of the backend is now implemented, we haven't implemented the
> user interface yet, so any ideas, no matter how wacky, are very welcome.
>
> Stefik
>
>
Other related posts:
