list attribute to define the timing of an image display

[liwenna]

Hi Daniel,

Could the problem be that the declaration of the variable that you're
referring too (1pcg1dur) is located on a different procedure than the
procedure in which it is referred too?

Most variables are only valid within their context (c.)... this
context is the procedure that they are on... I am not and ICT-educated
person (So DMCF please correct me if I state this all wrong!) but what
I get from it is that each of the variables and their references are
resolved on the procedure level and that references can not be
resolved to variables that are defined within a different procedure
(context...).

So.... the question is... in which procedure is this 1pcg1dur created
(i.e.  where is the dim line?). I got to guess that it is in  the
inline called 'initiatevar' that is locate on your sessionproc.

If so... the solution is simple: user created variables are variables
that somehow (...) overrule the whole procedure-defined context-
thing... find your script window and in the lower left corner go to
the tab called user. Here you located your dimline (dim 1pcg1dur as
integer). Remove that same line from the initatevar inline. The
initiatevarinline can keep the line stating "1pcg1dur = 1200".

The above might solve your problem... or you might have already have a
set-up like this in which case I have no clue what's going on :)

best,

AW

On Feb 3, 11:08 am, Michiel Spape <Michiel.Sp... at nottingham.ac.uk>
wrote:
> Hi Daniel,
> So, if I understand you correctly, you have something like:
> BlockList (with attribute IpCg1Dur, for instance)
> -Which runs some procedure, BlockProc
> --Which has TrialList, in which attribute Target1Dur is actually a reference to higher order IpCg1Dur.
> Something like that? This should actually work - the error you get suggests the TrialList can't 'find' attribute IpCg1Dur, which is either because of it is not within BlockList, or there's some other error going on. I do find E-Prime sometimes making a bit of a mess of attributes at the 'block' level and those at the 'trial' level (which you can easily see for yourself if you look at the generated .edat (use e-recovery on the .txt output should you not have one) - there'll be independent block / trial / subtrial columns) - with me, this often leads to some confusion.
> A suggestion, is to use one or more nested lists instead of referencing deeper and sometimes non-referable levels.
>
> Best,
> Michiel
>
> Michiel Spapé
> Research Fellow
> Perception & Action group
> University of Nottingham
> School of Psychologywww.cognitology.eu
>
> -----Original Message-----
> From: e-prime at googlegroups.com [mailto:e-prime at googlegroups.com] On Behalf Of Daniel
> Sent: 03 February 2011 04:48
> To: E-Prime
> Subject: list attribute to define the timing of an image display
>
> Hi,
>
> What I am trying to do is to use a list attribute to define the timing
> of an image display. This works perfectly fine if I use something like
> 1200 (to define a timing of 1200ms). But if I use an integer variable
> (ie. [IpCg1Dur] ) that is defined as 1200ms I get an error that says,
> "Factor Error: Can't resolve [IpCg1Dur] in this context." Is there a
> way to have an integer placeholder name in brackets as an attribute to
> inform an imagedisplay of the correct timing? The reason I want to do
> this is I am looking for a more efficient way to run a stop-switch
> task. This allows me to have only one procedure record all go and
> switch conditions instead of having separate procedures for each
> condition.
>
> http://i1139.photobucket.com/albums/n551/Danielw47181/E-primelistattr...
>
> That is a picture of what I am talking about. Sorry I could not figure
> out how to get the picture larger. If you go 9 columns across you will
> see the integers in [blue]. [Target1dur] is referenced in Target1 and
> [Target2dur] is referenced in Target2 to define the timing.
>
> Hope this makes sense
>
> Thanks
>
> --
> 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 athttp://groups.google.com/group/e-prime?hl=en.
>
> This message and any attachment are intended solely for the addressee and may contain confidential information. If you have received this message in error, please send it back to me, and immediately delete it.   Please do not use, copy or disclose the information contained in this message or in any attachment.  Any views or opinions expressed by the author of this email do not necessarily reflect the views of the University of Nottingham.
>
> This message has been checked for viruses but the contents of an attachment
> may still contain software viruses which could damage your computer system:
> you are advised to perform your own checks. Email communications with the
> University of Nottingham may be monitored as permitted by UK legislation.

-- 
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.