[visionegg] Re: black screen

A wiki sounds interesting.  I'm happy to just add some task modules to
the demo section via cvs, but I'm not a developer.  My sourceforge
username is psdlw (eg, http://eeg.sf.net).

I wonder if the visionegg is limited to visual stimuli?  I presume it
is possible to extend it to auditory stimuli.  I will do some homework
on pygame to better understand that.

Anyhow, I did pick up the distinction between the
VisionEgg.FlowControl module and using your own flow control.  That
was made clear in the programmers manual.  I would like to better
understand the FlowControl module, it looks like an interesting
construct.  I have some mind-bending to do before I can master how it
works.  It's challenging my often linear programming habits and that's
a good thing.

On Fri, 18 Mar 2005 10:53:03 -0800, Andrew Straw <astraw@xxxxxxxxxxx> wrote:
> Hi Darren et al. Sorry, I've been really busy lately and haven't even
> performed triage to see which questions are simple (and simply answered)
> versus which require a bit more care...  I hope to have some time this
> weekend.
> 
> As far as the .parameters attribute, it is essential for a variety of
> reasons, the most important of which being the pre-Python 2.2 history of
> the Vision Egg, where other name assignment tricks weren't possible.
> One thing it should do, though, is raise a warning if you assign to a
> parameter that doesn't exist, protecting you in the future from mistakes
> like screen.parameters.bcgolor = blah (note the misspelling).  If
> screen.bgcolor exists, it is a convenience for reading the variable made
> for backwards compatibility, and would perform no purpose if assigned
> to.  For this reason, perhaps I should scour the code and remove all
> instances of it.
> 
> I did, once upon a time, have a wiki online which I removed because I
> didn't feel that I could perform appropriate quality control on it and
> the amount of information there was rather limited.  (I'm sure this was
> not helped by removing it...)  However, I think Gabriel's suggestion of
> more user contributed example code is undoubtedly the way forward, and
> perhaps a wiki is the best way to go.  I know some projects have been
> subject to increasingly sophisticated forms of wiki spam, so I think I'd
> have to implement logins or something.  Of course, for this to be a
> success, people would really have to contribute code back.
> 
> Darren, can you at least tell me if, as a newbie, you came across the
> distinction of using the VisionEgg.FlowControl module and using your own
> flow control?  I can completely understand if the VisionEgg.FlowControl
> is a little mind-bending at first -- it's meant to solve some delicate
> issues like a stimulus moving to maintain a state of motion adaptation
> between experimental trials and so forth.  Quite possibly this is more
> than what most people need, but for a lot of my experiments it was quite
> necessary.
> 
> Wishing I had more time,
> Andrew
> 
> Darren Weber wrote:
> > OK, thanks.  I figured that the word 'parameters' was superfluous, so
> > screen.bgcolor should suffice.  Sorry I did not look at all demos in
> > the 5 mins I took to look into this problem.
> >
> >
> > On Fri, 18 Mar 2005 13:21:00 -0500, Mark Halko <mhalko@xxxxxx> wrote:
> >
> >>A common question:
> >>set the parameter like so:
> >>screen.parameters.bgcolor = (0.0, 0.0, 0.0, 0.0)
> >>
> >>This is in the following demos:
> >>az_el_grid.py
> >>convert3d_to_2d.py
> >>displayText.py
> >>dots.py
> >>dots_simple_loop.py
> >>lib3ds-demo.py
> >>makeMovie.py
> >>makeMovie2.py
> >>mouseTarget.py
> >>mouseTarget_user_loop.py
> >>multi_stim.py
> >>put_pixels.py
> >>quicktime.py
> >>target.py
> >>
> >>The code :
> >>screen = get_default_screen()
> >>generates a default Screen object
> >>http://www.visionegg.org/reference/VisionEgg.Core.Screen-class.html
> >>
> >>You can manipulate parameters of objects by referencing them with dot
> >>notation
> >>MyObject.parameters.MyParameter
> >>
> >>print MyObject.parameters.MyParameter
> >>will print the value of the parameter
> >>
> >>MyObject.parameters.MyParameter = NewValue
> >>sets the parameter to a new value
> >>
> >>On Mar 18, 2005, at 12:42 PM, Darren Weber wrote:
> >>
> >>
> >>>Hi,
> >>>
> >>>the construct
> >>>
> >>>screen = get_default_screen()
> >>>
> >>>creates a gray screen.  The reference documentation for the screen
> >>>class indicates that it has a bgcolor parameter.  I've tried a number
> >>>of ways to set it, without success.  How do we set this parameter?  I
> >>>want, bgcolor = (0.0, 0.0, 0.0), rather than the default gray.
> >>>
> >>>Best, Darren
> >>>======================================
> >>>The Vision Egg mailing list
> >>>Archives: http://www.freelists.org/archives/visionegg
> >>>Website: http://www.visionegg.org/mailinglist.html
> >>>
> >>
> >>======================================
> >>The Vision Egg mailing list
> >>Archives: http://www.freelists.org/archives/visionegg
> >>Website: http://www.visionegg.org/mailinglist.html
> >>
> >
> > ======================================
> > The Vision Egg mailing list
> > Archives: http://www.freelists.org/archives/visionegg
> > Website: http://www.visionegg.org/mailinglist.html
> >
> 
> --
> Andrew D. Straw  Post-doctoral scholar
> ,-.              Dickinson Lab
> \_/              California Institute of Technology
> 8||}             Mailcode 138-78
> / \              Pasadena CA 91125, USA
> `-^
>                   email:  astraw@xxxxxxxxxxx
>                  office: +1 626 395 4396
> 
> ======================================
> The Vision Egg mailing list
> Archives: http://www.freelists.org/archives/visionegg
> Website: http://www.visionegg.org/mailinglist.html
>
======================================
The Vision Egg mailing list
Archives: http://www.freelists.org/archives/visionegg
Website: http://www.visionegg.org/mailinglist.html

Other related posts: