string input with spaces

[Matthew]

Hi Liw, Dave,

Great advice!  We had tried using the space character based on what
was in the datafile, but didn't think to expand the column in the
spreadsheet to reveal the other character of interest, {ENTER}.  I'm a
little surprised that the termination response is logged actually, but
only when Allowable is {ANY} and Advanced... Response Mode is ALL.  I
have a similar script that has both these set to AlphaNumeric, and
{ENTER} terminates the response but is never logged.

Wouldn't be hard to clean these out of the datafile either via the
EPrime script or a VB macro afterwards, but since only an "educated"
few will be looking at this data, I don't feel like its necessary.

I'll cross-post this to my SOS on PST's forums.

Best,
-Matt




On Apr 14, 5:01 pm, David McFarlane <mcfar... at msu.edu> wrote:
> Matt,
>
> Stock reminder:  1) I do not work for PST.  2) PST's trained staff
> takes any and all questions athttp://support.pstnet.com/e%2Dprime/support/login.asp, and they
> strive to respond to all requests in 24-48 hours -- this is pretty
> much their substitute for proper documentation, so make full use of
> it.  3) If you do get an answer from PST Web Support, please extend
> the courtesy of posting their reply back here for the sake of others.
>
> That said, here is my take...
>
> In your .edat files, take a look at your .RESP value strings, and
> compare those to the strings in your Correct attribute.  Does the
> subject's RESP have a "{SPACE}" wherever they entered a space
> character?  Then your Correct attribute has to do the same.  Please
> see the "{key} nomenclature" topic in the online E-Basic
> Help.  Alternatively, you could add inline code to replace the {key}
> nomenclature with proper text, as in the example provided by PST's
> own Matt Lenhart athttp://www.pstnet.com/forum/Topic2194-5-1.aspx (must register &
> login to download).
>
> -- David McFarlane, Professional Faultfinder
>
> At 4/14/2011 10:39 AM Thursday, you wrote:
>
>
>
>
>
>
>
> >Hi all,
>
> >I have trouble with a problem solving experiment a student in a class
> >I'm TAing put together.  Rebus puzzles (e.g.
> >http://preview.tinyurl.com/3s73mwj)
> >are being used as the task.  The answers to these puzzles are short
> >idioms or sayings (e.g. "a cut above the rest").
>
> >The script has a slide which presents the puzzle stimulus (picture
> >file) and echoes input from the keyboard.  Problem is, when the answer
> >held in  our [CorrectAnswer] attribute is a string that contains
> >spaces, we either get an error message "Correct is not part of
> >allowable," or the script fails to recognize that a correct answer has
> >been provided.  I've mucked around with various settings of allowable
> >input in the Duration/Input and Echo submenus of the SlideObject, and
> >am having trouble remembering which mapped to which.
>
> >I think the problem is somewhere in how the input is being parsed and
> >compared to the value held in the list attribute [CorrectAnswer].  Our
> >current workaround is to omit spaces from all responses, but it seems
> >like the fix should be fairly simple (whatever it is).  Am happy to
> >send a copy of the experiment on request.
>
> >Thanks for your help,
> >-Matt

-- 
You received this message because you are subscribed to the Google Groups "E-Prime" group.
To post to this group, send email to e-prime at googlegroups.com.
To unsubscribe from this group, send email to e-prime+unsubscribe at googlegroups.com.
For more options, visit this group at http://groups.google.com/group/e-prime?hl=en.